Bug 181157

Summary: CSS padding information lost for <menclose>
Product: WebKit Reporter: Minsheng Liu <lambda>
Component: MathMLAssignee: Nobody <webkit-unassigned>
Status: NEW    
Severity: Normal CC: fred.wang
Priority: P2    
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
CSS padding information lost for <menclose> none

Minsheng Liu
Reported 2017-12-26 01:42:04 PST
Created attachment 330189 [details] CSS padding information lost for <menclose> See the attachment for a description of the bug. Two things bother me: 1. There is quite a lot code duplication between RenderMathMLRow and RenderMathMLEnclose’s layoutBlock. 2. How margin/padding/border is handled is unclear. The standard says > Because of this difference, applications that support MathML natively may choose to restrict the CSS properties applicable to MathML layout schemata to those properties that do not affect layout. (https://www.w3.org/TR/MathML3/chapter6.html#world-int-style) Should we ignore margin/padding/border altogether?
Attachments
CSS padding information lost for <menclose> (815 bytes, text/html)
2017-12-26 01:42 PST, Minsheng Liu 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Frédéric Wang (:fredw)
Comment 1 2018-01-04 05:02:30 PST
(In reply to Minsheng Liu from comment #0) > > Because of this difference, applications that support MathML natively may choose to restrict the CSS properties applicable to MathML layout schemata to those properties that do not affect layout. > > (https://www.w3.org/TR/MathML3/chapter6.html#world-int-style) > > Should we ignore margin/padding/border altogether? As I say in bug 181159 comment 2 ; I think we could probably ignore them for now.
Note You need to log in before you can comment on or make changes to this bug.