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?

>>723

What do you think will be the hardest part on the browser?

JavaScript

Could you make a release of what you have so far once the CSS layout is done?

Once Acid2 passes.

>>724
What do you mean exactly by "secure"? It seems everyone is throwing this word around like some kind of holy grail when it could mean anything from DRM and other user-hostile shit (fuck no, it's not going to be "secure" if you mean that) to buffer overflows (won't happen, there's very little dynamic allocation and what there is will have lengths checked very thoroughly...)

just tedious with all the tiny bits of configurability that it needs to support.

Calculating widths/heights is the most annoying part. One of the reasons why it's taking so long is because I'm trying to simplify it --- the spec is almost always more verbose and complex than it needs to be. Earlier in this thread I shrunk the HTML tokeniser from the absolutely bloated spec into a <1KB binary, so I expect some level of savings for the CSS parser and renderer... optimisation comes naturally from design.