Summary: | Support cast from CSSPrimitiveValue to unsigned, and use in appropriate places in CSSStyleSelector::applyProperty | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Luke Macpherson <macpherson> | ||||
Component: | New Bugs | Assignee: | Luke Macpherson <macpherson> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | Normal | CC: | eric, macpherson, mitz, simon.fraser, tony, webkit.review.bot | ||||
Priority: | P2 | ||||||
Version: | 528+ (Nightly build) | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Attachments: |
|
Description
Luke Macpherson
2011-08-15 22:44:24 PDT
Created attachment 104008 [details]
Patch
Comment on attachment 104008 [details]
Patch
Seems previously it would ignore bad values, and now this will ASSERT on bad values, is that a correct reading? Could you end up getting the grammar to hand the style-selector a non-number here?
That is correct, and it should be an assert because anything other than a number would indicate a bug in CSSParser.cpp:1524 - 1528 case CSSPropertyWebkitBoxFlex: validPrimitive = validUnit(value, FNumber, m_strict); break; case CSSPropertyWebkitBoxFlexGroup: case CSSPropertyWebkitBoxOrdinalGroup: validPrimitive = validUnit(value, FInteger | FNonNeg, true); As you can see only the appropriate types are considered valid. Comment on attachment 104008 [details] Patch Clearing flags on attachment: 104008 Committed r93263: <http://trac.webkit.org/changeset/93263> All reviewed patches have been landed. Closing bug. |