Bug 136188

Summary: Whether empty spans are rendered depends on their position
Product: WebKit Reporter: Nathan Carter <ncarter>
Component: New BugsAssignee: Nobody <webkit-unassigned>
Status: RESOLVED CONFIGURATION CHANGED    
Severity: Normal CC: ahmad.saleem792, hyatt, simon.fraser
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Mac   
OS: OS X 10.9   
URL: http://jsfiddle.net/aoh4fa50/8/
Attachments:
Description Flags
very small test case; see description for details
none
screenshot comparing rendering result on Firefox 31.0 and WebKit nightly none

Description Nathan Carter 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.
Comment 1 Nathan Carter 2014-08-22 18:37:02 PDT
Created attachment 237019 [details]
screenshot comparing rendering result on Firefox 31.0 and WebKit nightly
Comment 2 Ahmad Saleem 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!