Bug 1596979 Comment 10 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Correct, not a regression. (It feels like a regression from a user's perspective, but under the hood it's just a different behavior due to taking a different path in the UA-sniffing.  Plus, the regression-range is far back enough that it's not like users have been using this site successfully in Firefox recently & expecting it to continue working, so there's no urgency there either.)

Emily: I'd suggest we close this as a duplicate of bug 376027, and add a note on https://github.com/webcompat/web-bugs/issues/43632 saying that:
 (1) the site is simply running into that bug (the filter is failing to render because it's defined in a `display:none` subtree) 
 (2) if we like, we can do outreach to the site to suggest that they work around it by removing `display:none` from their `<svg>` element (and hiding it by another means, perhaps by changing the `#filters` rule to `#filters { display block; height: 0}` instead, which seems to have no effect on the layout).

(Someone on the webcompat team might do some outreach, if e.g. they speak Russian and can find an appropriate contact email.)
Correct, not a regression. (It feels like a regression from a user's perspective, but under the hood it's just a different behavior due to taking a different path in the UA-sniffing.  Plus, the regression-range is far back enough that it's not like users have been using this site successfully in Firefox recently & expecting it to continue working, so there's no urgency there either.)

Emily: I'd suggest we close this as a duplicate of bug 376027, and add a note on https://github.com/webcompat/web-bugs/issues/43632 saying that:
 (1) the site is simply running into that bug (the filter is failing to render because it's defined in a `display:none` subtree) 
 (2) if we like, we can do outreach to the site to suggest that they work around it by removing `display:none` from their `<svg>` element (and hiding it by another means, perhaps by changing the `#filters` rule to `#filters { display block; height: 0}` instead, which seems to make the svg element have no effect on the layout, which is good).

(Someone on the webcompat team might do some outreach, if e.g. they speak Russian and can find an appropriate contact email.)

Back to Bug 1596979 Comment 10