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?

>>218
Yes, I'm leaning towards "not at all".

The animation stuff (http://www.w3.org/TR/css3-animations/ ) is conceptually easy as all it's doing is modifying properties periodically (and forcing a relayout/redraw), but it's still quite superfluous to the goals of this browser: display the useful content, minimise the eyecandy and extra fluff.

Transformations are also conceptually simple, but implementation is going to involve a lot of extra bitmaps to be rendered to and plenty of pixel-shoving, which would probably be better done on a GPU... again, not a really useful/important thing to have for just displaying documents.

code coming out looking more like a poor man's Macromedia Flash.

I'd rather write a low-bloat Flash-compatible plugin instead (and I actually have a piece of one written already, for a demo over a decade ago); SWF is a great format that Adobe really fucked up when they bought Macromedia.