kjg-rauenberg.de - A black square around the text incorrectly displayed
Categories
(Web Compatibility :: Site Reports, defect, P3)
Tracking
(Webcompat Priority:P3, Webcompat Score:1)
People
(Reporter: railioaie, Unassigned)
References
(Depends on 1 open bug, )
Details
(Keywords: spec-needed, webcompat:needs-diagnosis, webcompat:site-report, Whiteboard: [webcompat-source:web-bugs])
User Story
platform:windows,mac,linux,android impact:minor-visual configuration:general affects:all branch:release diagnosis-team:layout user-impact-score:2
Attachments
(1 file)
568.90 KB,
image/png
|
Details |
Environment:
Operating system: Mac OS X 10.15
Firefox version: Firefox 135.0
Preconditions:
Clean profile
Steps to reproduce:
- Navigate to: https://kjg-rauenberg.de/aktionen/zeltlager/
- Scroll down
- Observe
Expected Behavior:
The text is displayed correctly without a square arround him
Actual Behavior:
A black square is displayed incorrectly around the text
Notes:
- Reproduces regardless of the status of ETP
- Reproduces in firefox-nightly, and firefox-release
- Does not reproduce in chrome
Created from https://github.com/webcompat/web-bugs/issues/149012
![]() |
||
Comment 2•26 days ago
•
|
||
I can reproduce the issue on Nightly137.0a1 Windows11, but not on Chrome.
The iframe has frameborder="none"
attribute.
However, on Firefox, the following browser style is applied.
resource://gre-resources/html.css
iframe {
border: 2px inset;
}
Workaround:
iframe[frameborder="none"] {
border: none;
}
Updated•24 days ago
|
Comment 3•23 days ago
|
||
Simon, is this something we could add to the default UA stylesheet, maybe?
Comment 4•22 days ago
|
||
HTML has a rule already:
But WebKit and Chromium don't have this rule, instead they have:
It seems to me the spec and Gecko should align with WebKit/Chromium. I'll file a spec issue.
Updated•22 days ago
|
Comment 5•21 days ago
|
||
Spec PR: https://github.com/whatwg/html/pull/11103
I suppose this should have a Core bug. :denschub can you file and set up dependencies?
Comment 6•16 days ago
|
||
I've filed the Core bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1952885
Description
•