? NPM Resource Changed ? Pending

User tests: Successful: Unsuccessful:

avatar laoneo
laoneo
24 Oct 2021

Followup pr of #35332.

Summary of Changes

As #35332 gets abandoned, this one here is a conflict fix. All the old commits should be preserved.

More information can be found in the pr #35332 by @JenSeReal.

Testing Instructions

Open media manager and execute the actions and browse around.

Actual result BEFORE applying this Pull Request

All should work.

Expected result AFTER applying this Pull Request

All should work.

avatar laoneo laoneo - open - 24 Oct 2021
avatar laoneo laoneo - change - 24 Oct 2021
Status New Pending
avatar joomla-cms-bot joomla-cms-bot - change - 24 Oct 2021
Category Administration com_media NPM Change JavaScript
avatar laoneo laoneo - change - 24 Oct 2021
Labels Added: NPM Resource Changed ?
avatar dgrammatiko
dgrammatiko - comment - 24 Oct 2021

@laoneo can you please run lint/fix? npm run lint:js -- --fix should do the trick

avatar richard67
richard67 - comment - 24 Oct 2021

@laoneo System test is failing, I've tried to restart several times now but it always fails at the same place, so maybe it's related to this PR: https://ci.joomla.org/joomla/joomla-cms/48082/1/22

It always fails at the test "Test that it is possible to navigate to a subfolder using double click.".

The screenshot from the test doesn't show anything special: https://ci.joomla.org/artifacts/joomla/joomla-cms/4.1-dev/35887/system-tests/48082

avatar laoneo laoneo - change - 24 Oct 2021
Title
[4.1] Refactor vue brower items
[4.1] Refactor vue browser items
avatar laoneo laoneo - edited - 24 Oct 2021
avatar dgrammatiko dgrammatiko - test_item - 24 Oct 2021 - Tested successfully
avatar dgrammatiko
dgrammatiko - comment - 24 Oct 2021

I have tested this item successfully on 3379fcc


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/35887.

avatar chmst chmst - test_item - 8 Nov 2021 - Tested successfully
avatar chmst
chmst - comment - 8 Nov 2021

I have tested this item successfully on 3379fcc

Tested as a user, without inspecting the code and English language. From a uses point of view the PR works good, no errors or notices found.


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/35887.

avatar laoneo
laoneo - comment - 8 Nov 2021

RTC

avatar richard67 richard67 - change - 8 Nov 2021
Status Pending Ready to Commit
avatar richard67
richard67 - comment - 8 Nov 2021

RTC


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/35887.

avatar richard67
richard67 - comment - 8 Nov 2021

Note for maintainers: When merging with a squash commit, don't remove the "co-authored by" tags in the commit description generated by GitHub so that the author of the original PR is not forgotten.

avatar wilsonge
wilsonge - comment - 8 Nov 2021

Can someone do some quick a11y validation on this one. I assume as we still have the unordered list it's ok. But some of the html here was refactored from divs to ul's originally for proper screenreader compat

avatar laoneo laoneo - change - 12 Nov 2021
Labels Added: ?
avatar laoneo
laoneo - comment - 12 Nov 2021

@brianteeman can you have a look on the concern from @wilsonge?

avatar brianteeman
brianteeman - comment - 12 Nov 2021

Please ask the accessibility team

avatar richard67
richard67 - comment - 12 Nov 2021

I will ping them on Glip.

avatar laoneo
laoneo - comment - 12 Nov 2021

@richard67 thanks

avatar dgrammatiko
dgrammatiko - comment - 12 Nov 2021

Can someone do some quick a11y validation on this one.

@wilsonge there are no structural changes here. The same HTML markup just moved around. (or am I wrong?)

avatar richard67
richard67 - comment - 12 Nov 2021

@dgrammatiko The thing is that while this PR was in progress, changes on the code which is moved around by this PR have been made, and so there were conflicts which were resolved. I think George just wants to be sure that the other changes have been applied to this PR when the conflicts were solved.

avatar laoneo
laoneo - comment - 12 Nov 2021

The conflicts were created by me as by #35451. I'v fixed them already. There were no structural changes involved in the other pr. I had a second look here and indeed, there are no structural changes as far as I can see, it was before also a list.

avatar carcam
carcam - comment - 12 Nov 2021

I can confirm there are no html structural changes from an a11y point of view. Whenever there should be a list, there is a list and no divs are involved. Also with this refactoring, checking the code and A11y fixes will be simpler as we will split longer code in vue components reusing the markup.

I do think this is a RTC!!

avatar richard67
richard67 - comment - 12 Nov 2021

Is is RTC already.

avatar laoneo
laoneo - comment - 12 Nov 2021

Thanks @carcam !!

avatar bembelimen bembelimen - change - 13 Nov 2021
Status Ready to Commit Fixed in Code Base
Closed_Date 0000-00-00 00:00:00 2021-11-13 23:10:57
Closed_By bembelimen
avatar bembelimen bembelimen - close - 13 Nov 2021
avatar bembelimen bembelimen - merge - 13 Nov 2021
avatar bembelimen
bembelimen - comment - 13 Nov 2021

Thx

Add a Comment

Login with GitHub to post a comment