Summary: | <style scoped>: rename matchRules() to matchRulesGlobally() to indicate that no scope is used | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Roland Steiner <rolandsteiner> | ||||||
Component: | CSS | Assignee: | Roland Steiner <rolandsteiner> | ||||||
Status: | RESOLVED INVALID | ||||||||
Severity: | Normal | CC: | dglazkov, dominicc, koivisto, macpherson, morrita, webkit.review.bot | ||||||
Priority: | P2 | ||||||||
Version: | 528+ (Nightly build) | ||||||||
Hardware: | All | ||||||||
OS: | All | ||||||||
Bug Depends on: | |||||||||
Bug Blocks: | 49142, 67720 | ||||||||
Attachments: |
|
Description
Roland Steiner
2011-11-16 02:11:02 PST
Created attachment 115350 [details]
Patch
Comment on attachment 115350 [details]
Patch
I suprised scoped matching would use a different matching function on this level. Why? (please cc me to all these)
This feels like a name that could be confusing when you are not actively working on scoped stye code. Perhaps "...InGlobalScope" would be more clear? Created attachment 115516 [details]
patch, matchRulesInGlobalScope
I like matchRulesInGlobalScope()! New patch with this name uploaded.
(In reply to comment #2) > (From update of attachment 115350 [details]) > I suprised scoped matching would use a different matching function on this level. Why? (please cc me to all these) matching Author rules will be done both globally and scoped, while other rules are matched globally only. With the rules themselves not carrying the scope, I feel the function name should make it explicit that no scoping will take place. Comment on attachment 115516 [details] patch, matchRulesInGlobalScope I added some comments to bug 67720. I'd like to see a more narrowly focused full patch before doing any code changes for this feature. It's probably better to do the renaming after the functionality has landed, to avoid confusion. Marking this as invalid for now. |