User tests: Successful: Unsuccessful:
Run npm run build:css
Go to System > Language Overrides
Create a new override
Click cursor in Search Text field
Status | New | ⇒ | Pending |
Category | ⇒ | Administration com_languages |
I don't see any difference, with or without the patch. Can you supply a screen shot showing what to look for?
Same for me. In both cases without and with this PR I have the popup message above the search box.
thats why screenshots are so helpful ;)
thats why screenshots are so helpful ;)
Agree.
Beside that, this status message seems to be a tricky thing. Currently it doesn't show up at all, whatever I do.
Ahhh .. you have to clear the cache in the list view so the message about cache recreation is shown when entering the search box in the edit view.
was just typing that info for you ;)
I have tested this item
Very tricky to reproduce the issue.
But I can confirm that this PR solves that issue.
I am fairly certain that this breaks the accessibility by putting the message in a new div instead of inside the input div
Even with aria-hidden="true"
for the message?
that is on the icon not on the text. You want the text to be accessible and connected to the input
I have not tested this item.
Changing back to not tested until some feedback from an accessibility expert.
Below the Search Text Field I see a brief message: 'Please Wait while the cache is recreated' on the first click only, with an without the patch. It most vanishes instantly. Clearing the cache in the list view does not make it reappear. It does reappear if I select a different client or language. As far as I can tell the patch does nothing!
Updated with screenshots in the original post.
I am using a Macbook Pro - a screen grab is 2880 x 1498 but I think the horizontal resolution is really 1440. I only see the message below the Search Text field so I guess it has already wrapped - mystery solved.
Not sure if it is a a11y issue. IBut also for sighted users it would be nice to hide the input group while the search is going on.
Category | Administration com_languages | ⇒ | Accessibility Administration com_languages |
@Quy There is no need to put the span .help-block
in a new div outside div .input-group
.
It seems that .input-group
is styled with display: flex;flex-wrap: wrap;
.
Just add add flex-basis: 100%
to .help-block
the issue is solved.
Can you adjust your PR with this change?
Run npm build:css
after applying the patch to test the change.
Labels |
Added:
?
|
Category | Administration com_languages Accessibility | ⇒ | Repository NPM Change Accessibility |
Labels |
Added:
NPM Resource Changed
|
Category | Accessibility Repository NPM Change | ⇒ | Administration com_languages Repository NPM Change Accessibility |
Just add add
flex-basis: 100%
to.help-block
the issue is solved.
With reverting your changes the className .help-block
is gone too.
Please adjust your PR to a flex-basis on #refresh-status
only.
I always prevent touching with id's and try to work with classNames instead.
But using id #refresh-status
is consistent with the rest of the css document.
Done. Thanks!
For those who want to test this issue.
After applying the patch you have to run npm run build:css
.
After reverting the patch you should run the same command again.
I have tested this item
run command npm run build:css
after applying the page to see the change
I have tested this item
Status | Pending | ⇒ | Ready to Commit |
rtc
Status | Ready to Commit | ⇒ | Fixed in Code Base |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2020-07-24 06:15:02 |
Closed_By | ⇒ | infograf768 | |
Labels |
Added:
?
|
Tks
I don't see any difference, with or without the patch. Can you supply a screen shot showing what to look for?
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/30096.