3 ms·
1. Remove legacy HTML support. HTML should become a format agnostic DOM. Without any scope of inline style or scripting. So even a markdown document could possi
by sudiptadeb 5y ago
1. Remove legacy HTML support. HTML should become a format agnostic DOM. Without any scope of inline style or scripting. So even a markdown document could possibly be natively rendered albeit with limited element support
2. Styling should be done exclusively out of band. CSS is a great tool, but a massive decluttering is required. Native can also be a supported styling option.
3. Same out of band scripting. JS is fine. Support can become language agnostic. wasm and others will come under this.
In conclusion the browser should become a decoupled selectable network of Markup, Styling and Scrpting. So when the developer wants they can style the components with native android widgets or canvas and when they want they can write the business logic in Swift or Rust or Dart
I see browser as a framework provider for native apps with prebaked features like assessibility, multiple input devices, sandboxing, etc