I would separate the app-rendering and document-rendering, but in a composable way. Document-rendering would be much like reader-mode today where the browser ap

I would separate the app-rendering and document-rendering, but in a composable way. Document-rendering would be much like reader-mode today where the browser applies a lot of styles to make the text beautiful and readable based on the user's preferences. App-rendering would have incredibly consistent default styles (such as no margins, no padding, no underline on links). Basically I feel that browser default styles are ugly because they are afraid to break the "app-rending". I think separating these would allow the browser to make document-rendering much nice. I wrote a blog post with more detail. https://kevincox.ca/2021/07/14/chrome-and-content-modes-in-html/ https://kevincox.ca/2021/07/14/chrome-and-content-modes-in-h... On the other side can a major browser fix keyboard shortcuts. I want 1. User controllable keyboard shortcuts. (Ideally with some sort of scripting or macro system) 2. Don't allow websites to override important browser shortcuts. Why can't I open my history when looking at a Google Doc?!