| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
class CORE_EXPORT CSSRouteRule final : public CSSRule {Should this be based on CSSConditionRule, and should DowncastTraits::AllowFrom allow the same downcast, to match the IDL?
kUrlPatternToken,I'm surprised to see a new token type, and I'm a little confused because I can't find anything in the CL that produces a kUrlPatternToken.
Looking at the rest of the code... could we just handle these as `<function-token>` and look for the url-pattern function name? Or if there are places where they can appear outside `url-pattern()` could those be `<string-token>`?
if (name.StartsWith("--")) {
// Don't clash with CSS @route rules.
return ParseResult(ParseResult::kTypeError,
"Route names cannot start with '--'");
}Do we have a WPT for this case?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Should this be based on CSSConditionRule, and should DowncastTraits::AllowFrom allow the same downcast, to match the IDL?
Thanks for spotting! It should be CSSRule, though. It's css_route_rule.idl that's wrong. Fixed it.
I'm surprised to see a new token type, and I'm a little confused because I can't find anything in the CL that produces a kUrlPatternToken.
Looking at the rest of the code... could we just handle these as `<function-token>` and look for the url-pattern function name? Or if there are places where they can appear outside `url-pattern()` could those be `<string-token>`?
Removed. Thanks! It was something I thought I needed, but then I removed most of it again (apart from this one, clearly).
I'm unfamiliar with this code, and looked to the `url()` implementation for inspiration. Maybe not the best choice.
if (name.StartsWith("--")) {
// Don't clash with CSS @route rules.
return ParseResult(ParseResult::kTypeError,
"Route names cannot start with '--'");
}Do we have a WPT for this case?
Added TODO. Most likely all this code will go away, so I won't bother spending any time on it right now.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
kUsername = 903,I'm not sure about username/password here yet. Perhaps let's start without them? CC @dbaron perhaps let's remove these from the spec for now?
Also not sure about hostname.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
kUsername = 903,I'm not sure about username/password here yet. Perhaps let's start without them? CC @dbaron perhaps let's remove these from the spec for now?
Also not sure about hostname.
Since we're discussing... 😊
In general, instead of all these descriptors, I think it would be great if `url-pattern()` could be used for everything. I don't know what's possible, and then collapse it all to:
`@route --name (url-pattern(pathname:"/path/:id/", protocol:"https"));`
Then we also don't have to define what should happen if `pattern` is specified alongside other component descriptors.
(I don't think David got properly CCed)
kUsername = 903,Morten StenshorneI'm not sure about username/password here yet. Perhaps let's start without them? CC @dbaron perhaps let's remove these from the spec for now?
Also not sure about hostname.
Since we're discussing... 😊
In general, instead of all these descriptors, I think it would be great if `url-pattern()` could be used for everything. I don't know what's possible, and then collapse it all to:
`@route --name (url-pattern(pathname:"/path/:id/", protocol:"https"));`
Then we also don't have to define what should happen if `pattern` is specified alongside other component descriptors.
Maybe pattern after the syntax for `if()`?
interface CSSRouteRule : CSSConditionRuleShould this be derived from CSSRule as well? (Same in android_webview/...)
Should this be derived from CSSRule as well? (Same in android_webview/...)
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |