Summary: | Web Inspector: DOM tree search issue with quotation marks | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Alexander Pavlov (apavlov) <apavlov> | ||||
Component: | Web Inspector (Deprecated) | Assignee: | Alexander Pavlov (apavlov) <apavlov> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | Normal | CC: | apavlov, bweinstein, joepeck, keishi, loislo, pfeldman, pmuellr, rik, timothy, yurys | ||||
Priority: | P2 | ||||||
Version: | 528+ (Nightly build) | ||||||
Hardware: | All | ||||||
OS: | All | ||||||
Attachments: |
|
Description
Alexander Pavlov (apavlov)
2012-08-27 02:47:39 PDT
Created attachment 160688 [details]
Patch
Comment on attachment 160688 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=160688&action=review > Source/WebCore/inspector/InspectorDOMAgent.cpp:861 > + if (!exactAttributeMatch && attribute->localName().find(attributeQuery) != notFound) { Why did this change? I wonder if we could support the 'class="foo' or 'width=100%' case here. (In reply to comment #2) > (From update of attachment 160688 [details]) > View in context: https://bugs.webkit.org/attachment.cgi?id=160688&action=review > > > Source/WebCore/inspector/InspectorDOMAgent.cpp:861 > > + if (!exactAttributeMatch && attribute->localName().find(attributeQuery) != notFound) { > > Why did this change? I wonder if we could support the 'class="foo' or 'width=100%' case here. Fixed the inadvertent change. I'm not sure how we should handle the double quotes around the property values, and this might turn out to be a source of confusion for our users. Let's see what they ask for next. Committed r126749: <http://trac.webkit.org/changeset/126749> |