Bug 46591
Summary: | [Meta] Implement CSS parser in C++ | ||
---|---|---|---|
Product: | WebKit | Reporter: | Dimitri Glazkov (Google) <dglazkov> |
Component: | CSS | Assignee: | Dave Hyatt <hyatt> |
Status: | RESOLVED FIXED | ||
Severity: | Enhancement | CC: | abarth, annevk, ap, arv, cmarcelo, eoconnor, hyatt, jonlee, martijn, peter, phiw2, simon.fraser, skyul, webkit-bug-importer, webmaster |
Priority: | P2 | Keywords: | InRadar |
Version: | 528+ (Nightly build) | ||
Hardware: | All | ||
OS: | All | ||
Bug Depends on: | 161095, 161174, 161537, 161695, 161749, 161813, 161868, 161916, 161931, 162018, 162033, 162078, 165213 | ||
Bug Blocks: | 16708, 46590 |
Dimitri Glazkov (Google)
Get rid of the existing bison-based parser, implement our own parser, fix bugs and improve extensibility in the process
Attachments | ||
---|---|---|
Add attachment proposed patch, testcase, etc. |
Adam Barth
Is there a spec for how a CSS parser should work? Can we produce a spec at the same time as we produce the implementation?
Simon Fraser (smfr)
One major win here would be better error reporting.
Anne van Kesteren
There is nothing apart from the grammar plus prose combination the current specifications have. Having an HTML5-like specification for this would be really great.
Alexey Proskuryakov
I can already see a bug filed three years later: get rid of messy-crashy-buggy-slow manually maintained CSS parser code, replace it with autogenerated one :)
Radar WebKit Bug Importer
<rdar://problem/23146798>
Dave Hyatt
Turned on (see bug 165213).