Gabriel Welsche

@cortex THANKS a lot for your efforts! Hope you can solve the problem!

Great work! But difficult to understand, please remove sentences like > The _About_ is easy enough to understand. If the viewport is unspecified, the components/custom element _About_ should be loaded...

> `Authors` > The _authors+about_ instruction is in its full form _authors@lists_ + _about@default_ There is no viewport named _default_, do you mean _about@content_ ? Why is it necessary to...

your proposed syntax: `books+book=5+book-details=5` `books+book=3+book-details@books-tabs=3` I'd prefer web-form query string syntax https://en.wikipedia.org/wiki/Query_string#Web_forms . it's easy to transform, if all parameters are passed to viewport. My proposal `books?id=5&view-ports=book,book-details` => resolved to...

Thank you for your work and the explanations here!

I'd perfer the 1st mentioned solution: Document this gotcha and just let developers deal with it. > It demonstrates that this is a leaky abstraction/ the code they eventually have...

A very simple implementation (mvp) would satisfy most people, later the functionality could be improved ( similar to iterm2 / macOS Terminal).  

maybe the mvp could be implemented in vi mode (`/` `search pattern` `ENTER`") and `n` to find the next occurrence or `N` to find the previous.

👍 I would very much welcome it. It should not be complicated to implement this feature MVP: - Tags: create if not available; fuzzy (case sensitive, comma separated or as...