[Webkit-unassigned] [Bug 184798] New: overridden CSS rule for background-size changes button rendering from platform (GTK) to HTML
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Thu Apr 19 15:45:25 PDT 2018
https://bugs.webkit.org/show_bug.cgi?id=184798
Bug ID: 184798
Summary: overridden CSS rule for background-size changes button
rendering from platform (GTK) to HTML
Product: WebKit
Version: WebKit Nightly Build
Hardware: All
OS: Linux
Status: NEW
Severity: Normal
Priority: P2
Component: Layout and Rendering
Assignee: webkit-unassigned at lists.webkit.org
Reporter: mod-wkbz at mt2015.com
CC: bfulgham at webkit.org, simon.fraser at apple.com,
zalan at apple.com
Created attachment 338372
--> https://bugs.webkit.org/attachment.cgi?id=338372&action=review
page demonstrating inability to override CSS rules
In cases where buttons have not been "significantly" (my term) styled by web pages, WebKit will render them with platform-native appearance.
This has some relationship to the `-webkit-appearance` CSS property; for example, setting "-webkit-appearance: none;" disables it and renders such elements as plain colored rectangles.
Another property which affects the decision to render elements with platform-native appearance is `background-size`. Setting "background-size: 110%;" similarly causes non-platform-native rendering.
However, adding another CSS rule which overrides this first rule (as verified in the web inspector) does *not* restore platform-native appearance.
There seems to be no way to reset an element to platform-native rendering, even by setting the `appearance` or `-webkit-appearance` properties. This is a problem from an accessibility perspective, where user stylesheets may want to enforce native rendering for button elements where web pages set background-size.
The attached web page demonstrates the strange behavior observed here, which seems to contradict the notions of cascading/inheritance in CSS.
This is also the case for other native-themed elements, and likely for other CSS properties, but I don't have a good way to investigate exhaustively. I've observed this bug in WebKitGTK+ 2.4.11 with the WebKit2 API but this behavior is not new, reaching back at least to before the Webkit1 deprecation.
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20180419/75fab611/attachment.html>
More information about the webkit-unassigned
mailing list