Why browsers are bloated

https://github.com/WebKit/webkit/blob/master/Source/WebCore/platform/Scrollbar.cpp
https://github.com/WebKit/webkit/blob/master/Source/WebCore/platform/win/ScrollbarThemeWin.cpp
Let's reinvent the fucking scrollbar, which every goddamn platform with a UI already has, and make it behave subtly different from the native one!

Right-click a native scrollbar in some other app:
- Scroll Here
- Top
- Bottom
- Page Up
- Page Down
- Scroll Up
- Scroll Down

Right-click a scrollbar in Chrome:
- Back
- Forward
- Reload
- Save As...
...

Right-click a scrollbar in Firefox and Opera:
Absolutely fucking nothing happens!

What the fuck!? How did these terminally retarded idiots get involved in creating one of the most important pieces of software to the average user?

>>628
The majority of that page has to do with JS, which means it is completely irrelevant to my browser at the moment: it doesn't have JS yet, and I don't plan to think about the details of it anytime soon. JS features will likely be configurable on a per-site basis.

CSS media queries - this is CSS3, so it is basically ignored.
CSS fonts - needs JavaScript to work, so irrelevant.
CSS visited - user-configurable per-site, and I'm probably going to indicate visited/not-visited some other way through the UI anyway (e.g. status bar indication) so it's no big loss.
Plugins - user-configurable per-site.

User-Agent: your choice. Set it to whatever you want, or don't send one at all.
ETag tracking: not supported at all because there is currently no plans to do any caching.
"Do not track" header: useless bureaucracy bullshit. You draw more attention using it than not.

TLS/SSL Session IDs: irrelevant network layer concern, and depends what is doing SSL/TLS. The proxy I currently run everything through does not support session resumption at all.

Also, if I'm not posting any updates, then assume nothing has happened.