WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED CONFIGURATION CHANGED
136188
Whether empty spans are rendered depends on their position
https://bugs.webkit.org/show_bug.cgi?id=136188
Summary
Whether empty spans are rendered depends on their position
Nathan Carter
Reported
2014-08-22 18:36:10 PDT
Created
attachment 237018
[details]
very small test case; see description for details Visit the URL for this ticket
http://jsfiddle.net/aoh4fa50/8/
or the attached minimal test case to see an example. The inner span does not appear in the rendered version as it is positioned (i.e., its 1px border is not visible). However, if you move the span to a different location (e.g., after the A character) then it becomes visible. Alternately if you remove the outer span, then the inner span becomes visible. These changes seem like they should have no impact; the span should either be visible always or never, but not contingent on these trivial changes. (My vote is "always"!) This issue is discussed further at this StackOverflow question as well:
http://stackoverflow.com/questions/25456300/nested-styled-spans-render-differently-in-chrome-firefox-bug-or-feature
Tested in latest nightly,
r172857
.
Attachments
very small test case; see description for details
(95 bytes, text/html)
2014-08-22 18:36 PDT
,
Nathan Carter
no flags
Details
screenshot comparing rendering result on Firefox 31.0 and WebKit nightly
(190.57 KB, image/png)
2014-08-22 18:37 PDT
,
Nathan Carter
no flags
Details
View All
Add attachment
proposed patch, testcase, etc.
Nathan Carter
Comment 1
2014-08-22 18:37:02 PDT
Created
attachment 237019
[details]
screenshot comparing rendering result on Firefox 31.0 and WebKit nightly
Ahmad Saleem
Comment 2
2023-09-19 14:30:08 PDT
All browsers (Safari 16.6, Chrome Canary 119 and Firefox Nightly 119) are matching each other and nothing like reference screenshot. Marking this as 'RESOLVED CONFIGURATION CHANGED'. Thanks!
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug