Bug 156537 - Move parsing of operator attributes into the MathML element classes
Summary: Move parsing of operator attributes into the MathML element classes
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: MathML (show other bugs)
Version: WebKit Nightly Build
Hardware: All All
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on: 156792 159619 160034 160190 160239 160241 160245 160301 160336 160339
Blocks: 156536
  Show dependency tree / graph
 
Reported: 2016-04-13 07:56 PDT by Frédéric Wang (:fredw)
Modified: 2016-08-03 00:03 PDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Frédéric Wang (:fredw) 2016-04-13 07:56:13 PDT 
One more step for bug 156536. I think when we get rid of all anonymous nodes it should be easier to fix that bug.

Currently this code is in RenderMathMLOperator and MathMLOperatorDictionary.

The operator properties depend on explicit attributes, on dictionary values (which depends on the infix/prefix/postfix form) and on the position of the operator inside its container value (for the form value):

https://www.w3.org/TR/MathML3/chapter3.html#presm.mo.dict.attrs
https://www.w3.org/TR/MathML3/appendixc.html

Some are length values. See the related bug 118900.
Comment 1 Frédéric Wang (:fredw) 2016-07-11 07:38:06 PDT 
Extending this to all operator attributes we support. Here are they:

- fence
- separator
- stretchy
- symmetric
- largeop
- movablelimits
- accent
- form
- lspace
- rspace
- minsize
- maxsize
Comment 2 Frédéric Wang (:fredw) 2016-08-03 00:03:36 PDT 
All operator attributes are now parsed in element classes.