Bug 165737

Summary: [CSS Parser] Make sure content extensions initialize AtomicString
Product: WebKit Reporter: Dave Hyatt <hyatt>
Component: New BugsAssignee: Dave Hyatt <hyatt>
Status: RESOLVED FIXED    
Severity: Normal CC: commit-queue
Priority: P2    
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Patch
none
Patch none

Dave Hyatt
Reported 2016-12-10 15:34:32 PST
[CSS Parser] Make sure content extensions initialize AtomicString
Attachments
Patch (1.30 KB, patch)
2016-12-10 15:36 PST, Dave Hyatt 		no flags
DetailsFormatted DiffDiff
Patch (1.21 KB, patch)
2016-12-10 23:02 PST, Dave Hyatt 		no flags
DetailsFormatted DiffDiff
Show Obsolete (1) View All Add attachment proposed patch, testcase, etc.
Dave Hyatt
Comment 1 2016-12-10 15:36:13 PST
Created attachment 296826 [details] Patch
Dave Hyatt
Comment 2 2016-12-10 15:37:38 PST
Fixed in r209676.
Dave Hyatt
Comment 3 2016-12-10 21:16:05 PST
Had to roll this out.
Dave Hyatt
Comment 4 2016-12-10 23:02:23 PST
Created attachment 296855 [details] Patch
WebKit Commit Bot
Comment 5 2016-12-11 22:40:12 PST
Comment on attachment 296855 [details] Patch Clearing flags on attachment: 296855 Committed r209699: <http://trac.webkit.org/changeset/209699>
WebKit Commit Bot
Comment 6 2016-12-11 22:40:16 PST
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.