Christopher Joel
Christopher Joel
This seems like something that could fall under the umbrella of "solved by inheritance." For example, a user could implement a `carbon-route` derivative that has stricter matching semantics.
We spent very little time designing matching semantics for `carbon-route`. This was excusable because inheritance can allow us to offer a derived element with better semantics. That said, in your...
@rictic what are your thoughts on this?
@ebidel Updating page meta is fundamentally orthogonal to the design of the `` element. I like @AndreasGalster 's approach of building a separate element that can pair with `` to...
Is this purely documentation? I'm not sure we have an implemented strategy for this yet. /cc @rictic
It would be good to verify the behavior of using `#` to target a scroll point in the page under ShadowDOM. In the Polymer Elements case, we certainly have many...
I wonder if this is an opportunity for us to define specialized semantics for how hash links should work in an app that has several layers of ShadowDOM. Perhaps we...
In the normal flow of things, a `carbon-route` consumes a `route` and produces a `tail`. perhaps consuming a new `route` can stand-in as an opportune moment to let an observer...
> I think that you want to configure the loading promise on the route that's being navigated to This is what I intended to illustrate in my example. The `navigate`...
Depending on the implementation, I can imagine... - `` may need to know (and per my straw man, it would) - `` may need to know that it will no...