Bug 39853

Summary:

SPAN element not being rendered properly

Product:

WebKit

Reporter:

Aditya Mukherjee <aditya.vm>

Component:

Layout and Rendering

Assignee:

Nobody <webkit-unassigned>

Status:

RESOLVED WONTFIX

Severity:

Normal

CC:

ahmad.saleem792, ap

Priority:

Version:

528+ (Nightly build)

Hardware:

Mac (Intel)

OS:

OS X 10.5

Attachments:

Description	Flags
How the element appears in WebKit	none
All styles associated with the element	none
How the element should appear (taken in Firefox)	none

Aditya Mukherjee

Reported 2010-05-27 13:31:01 PDT

I am adding text to a SPAN element using an XHR call (shown in attached screenshot 1). However, the element remains at the same size as it would without the text, but it now contains the text. Nothing I do fixes it (even a 'display: block'). However, if I toggle any CSS property via Web Inspector, it fixes itself. This happens only on the first element, as a second element after it seems to render fine. This problem only exists in Webkit (I've tested it in Safari and Chrome); Firefox displays it properly (screenshot attached).

Attachments
How the element appears in WebKit (5.26 KB, image/png) 2010-05-27 13:31 PDT, Aditya Mukherjee	no flags	Details
All styles associated with the element (28.06 KB, image/png) 2010-05-27 13:32 PDT, Aditya Mukherjee	no flags	Details
How the element should appear (taken in Firefox) (5.49 KB, image/png) 2010-05-27 13:32 PDT, Aditya Mukherjee	no flags	Details
View All Add attachment proposed patch, testcase, etc.

Aditya Mukherjee

Comment 1 2010-05-27 13:31:41 PDT

Created attachment 57270 [details] How the element appears in WebKit

Aditya Mukherjee

Comment 2 2010-05-27 13:32:10 PDT

Created attachment 57271 [details] All styles associated with the element

Aditya Mukherjee

Comment 3 2010-05-27 13:32:37 PDT

Created attachment 57272 [details] How the element should appear (taken in Firefox)

Alexey Proskuryakov

Comment 4 2010-05-28 12:53:39 PDT

Could you please provide a test case? It is not feasible to re-create and fix this problem based on the above description alone.

Ahmad Saleem

Comment 5 2022-12-30 16:22:39 PST

Due to lack of testcase and vague explanation, it is difficult to fix this issue and since 2010, Web Standards are evolved and so does browser engines and these issues and quirks might have already being fixed in one way or another. If there will be some outstanding issue, they will already have other bugs to work on. Marking this as "RESOLVED WONTFIX" so focus can be made to other bugs. Thanks!

Note You need to log in before you can comment on or make changes to this bug.