RESOLVED FIXED 63657
Remove ElementWithPseudoId, since now an Element can store it all by itself.
https://bugs.webkit.org/show_bug.cgi?id=63657
Summary Remove ElementWithPseudoId, since now an Element can store it all by itself.
Dimitri Glazkov (Google)
Reported 2011-06-29 14:16:36 PDT
Remove ElementWithPseudoId, since now an Element can store it all by itself.
Attachments
Patch (19.19 KB, patch)
2011-06-29 14:18 PDT, Dimitri Glazkov (Google)
no flags
Patch for landing (19.21 KB, patch)
2011-06-29 16:23 PDT, Dimitri Glazkov (Google)
no flags
Dimitri Glazkov (Google)
Comment 1 2011-06-29 14:18:09 PDT
Kent Tamura
Comment 2 2011-06-29 14:55:06 PDT
Comment on attachment 99148 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=99148&action=review > Source/WebCore/html/ValidationMessage.cpp:135 > host->ensureShadowRoot()->appendChild(m_bubble.get(), ec); > nit: We had better have ASSERT(!ec);
Dimitri Glazkov (Google)
Comment 3 2011-06-29 16:23:04 PDT
Created attachment 99176 [details] Patch for landing
WebKit Review Bot
Comment 4 2011-06-29 17:03:49 PDT
Comment on attachment 99176 [details] Patch for landing Clearing flags on attachment: 99176 Committed r90071: <http://trac.webkit.org/changeset/90071>
WebKit Review Bot
Comment 5 2011-06-29 17:03:54 PDT
All reviewed patches have been landed. Closing bug.
Rafael Brandao
Comment 6 2011-06-30 13:35:11 PDT
Got this when I was building: Reading [...]/WebKit/Source/WebCore/WebCore.pro [[...]/WebKit/WebKitBuild/Release/WebCore] WARNING: Failure to find: html/shadow/ElementWithPseudoId.h Perhaps this patch caused this? It's building though, just an annoying warning.
Rafael Brandao
Comment 7 2011-06-30 13:45:59 PDT
(In reply to comment #6) > Got this when I was building: > > Reading [...]/WebKit/Source/WebCore/WebCore.pro [[...]/WebKit/WebKitBuild/Release/WebCore] > WARNING: Failure to find: html/shadow/ElementWithPseudoId.h > > Perhaps this patch caused this? It's building though, just an annoying warning. It'll be a quick fix, I'll handle that.
Note You need to log in before you can comment on or make changes to this bug.