Bug 13170

Summary: Incompatibility between run-in and margin/padding
Product: WebKit Reporter: David Latapie <david>
Component: New BugsAssignee: Nobody <webkit-unassigned>
Status: RESOLVED INVALID    
Severity: Normal CC: webkit
Priority: P2    
Version: 523.x (Safari 3)   
Hardware: Mac   
OS: OS X 10.4   
Attachments:
Description Flags
Testcase with both padding and margin none

David Latapie
Reported 2007-03-23 07:08:32 PDT
“margin” is not taken into consideration when using “run-in” (Webkit ToT). “padding” is not neither, but that may be normal. “margin” is taken into consideration with Opera. This is not a regression. See attached document.
Attachments
Testcase with both padding and margin (1.21 KB, application/xhtml+xml)
2007-03-23 07:10 PDT, David Latapie
no flags
David Latapie
Comment 1 2007-03-23 07:10:29 PDT
Created attachment 13778 [details] Testcase with both padding and margin
Robert Blaut
Comment 2 2008-02-24 03:11:08 PST
Why do you expect the <dt> which became inline box should have margin property? Margin applies only to block boxes. dt is no longer block box in this case. Opera behavior is incorrect. The bug report is INVALID.
David Latapie
Comment 3 2008-11-23 13:20:22 PST
I cannot say whether it is extended non-standard support or if it really was a bug from Webkit, but this now works in screen mode BUT not in print mode; furthermore, going yo print the text ends up in garbling the text in screen mode (Opera has it right, although the first example has extra lines between text). I reopen the bug, could someone change the status accordingly?
Robert Blaut
Comment 4 2008-12-29 04:46:16 PST
(In reply to comment #3) > I cannot say whether it is extended non-standard support or if it really was a > bug from Webkit, but this now works in screen mode BUT not in print mode; > furthermore, going yo print the text ends up in garbling the text in screen > mode (Opera has it right, although the first example has extra lines between > text). I reopen the bug, could someone change the status accordingly? > David, problem with printing run-in elements are actually known and it's tracked by bug 12522. The other mentioned issue is not a bug as I wrote above.
Note You need to log in before you can comment on or make changes to this bug.