Steps to reproduce
Expected results
Actual results
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| gerrit: workaround a CSS bug with Microsoft Edge | operations/puppet | production | +12 -0 |
Change 309385 had a related patch set uploaded (by Paladox):
Workaround a bug in gerrit on Microsoft Edge
I don't see a patch submitted in upstream, but a patch in Wikimedia Gerrit only? Why?
@Paladox: "affects users who use Microsoft Edge" (or "affects people living in some city in some country") is no logical argument related to a setting describing urgency, and the functionality does not seem to be the most critical one either. Please refrain from setting priorities until there is a clearer understanding what they are supposed to mean. Thanks! (No "Ok" reply needed here.)
The reason I only have a patch on our gerrit is because it is a workaround and not a fix. But isent a browser that users use on windows 10 important enough instead of setting it to low priority.
What happends if a user uses Microsoft edge but carnt clone because it dosent display it properly.
Why did you set it to low priority, I doint see this as low priority.
Please explain what you think is high priority, low priority since browsers not displaying properly should be counted as high priority.
Not everyone uses chrome or firefox.
There is always [[ https://www.mediawiki.org/wiki/Gerrit/Tutorial | git review -d 123456 ]] as a workaround, no matter which browser users use.
See this page for Priority level explanations. (Any debating of the meaning of those levels is off-topic for this task.)
Re opening as the workaround will only work for logged in users not logged out users since it will only show the anon http selection and not http and ssh.
I belive this may be a bug in Microsoft Edge, I've reported it to them so hopefully it will be fixed soon. I'm not 100% sure it is a bug in Edge but anyways ive reported it. This task should stay open until it is fixed in gerrit or edge.
According to them the bug does not exist currently in the public released version, ie the annerversery update but does in the windows insider build, they say there is a fix internally but I doint know if it is now in the public release of windows insider build since the last response was September 20 2016.
This was broken on insider releases when they first released new build in mid agust this doesn't affect production versions.
This is now fixed in build 14942. I've confirmed it is fixed and closing as resolved now :)