WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
150391
Web Inspector: Typo in a property name: style.inerhited
https://bugs.webkit.org/show_bug.cgi?id=150391
Summary
Web Inspector: Typo in a property name: style.inerhited
Nikita Vasilyev
Reported
2015-10-21 05:05:05 PDT
Should be "inherited". WebStorm spotted a missing property, otherwise I wouldn't notice.
http://trac.webkit.org/changeset/187195
https://github.com/WebKit/webkit/blob/f83708780100ed4be51a136ec33b3ddfdddcc9dd/Source/WebInspectorUI/UserInterface/Views/RulesStyleDetailsPanel.js#L293
I searched in Source/WebInspectorUI. That's the only place where "inerhited" is used.
Attachments
Patch
(1.60 KB, patch)
2015-10-21 05:07 PDT
,
Nikita Vasilyev
no flags
Details
Formatted Diff
Diff
View All
Add attachment
proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1
2015-10-21 05:05:42 PDT
<
rdar://problem/23199935
>
Nikita Vasilyev
Comment 2
2015-10-21 05:07:44 PDT
Created
attachment 263675
[details]
Patch
Nikita Vasilyev
Comment 3
2015-10-21 06:03:37 PDT
I've been looking at this over 300 lines long refresh method for a while and I still don't quite understand what difference fixing this typo made. Devin, in insertAllMatchingPseudoStyles(force), what is the point of the force agrument?
WebKit Commit Bot
Comment 4
2015-10-21 06:37:36 PDT
Comment on
attachment 263675
[details]
Patch Clearing flags on attachment: 263675 Committed
r191387
: <
http://trac.webkit.org/changeset/191387
>
WebKit Commit Bot
Comment 5
2015-10-21 06:37:39 PDT
All reviewed patches have been landed. Closing bug.
Devin Rousso
Comment 6
2015-10-21 10:07:31 PDT
(In reply to
comment #3
)
> I've been looking at this over 300 lines long refresh method for a while and > I still don't quite understand what difference fixing this typo made. > > Devin, in insertAllMatchingPseudoStyles(force), what is the point of the > force agrument?
The idea behind the force argument was that pseudo-element styles (::before, ::after, etc) should never be seen below user-agent or inherited rules. They should always be inserted before the first of those rules in the absolute worst case. On most websites, there will be a matching rule that doesn't have the pseudo-element, so this is not necessary (like having ".example" and ".example::before"). It is possible, however, to have pseudo-rules without a matching non-pseudo-element rule, and it is for this case that the force was added. Example: on a blank page, create a rule and give it the selector "body::before" (and give the ::before a content). This pseudo-element rule should appear before the user-agent "body" rule.
Nikita Vasilyev
Comment 7
2015-10-21 14:13:01 PDT
Thanks Devin, that makes sense now.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug