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?

I am surprised at 2 things, aftyer not being here in more than a year:

1. this server and domain still live
2. this thread is alive

Cudder, you are one heck of a trooper.

Reviewing the thread, I had an epiphany. Knowing that HTML and CSS are shit markup languages, and you are using ASM to build your browser, why not form new methods to represent the DOM values that are their specifications. It'd make for easier parsing and algorithms, by performing new methods of their representations.

Here's one raw example to illustrate my point by no means the one I want implemented:
Element, name, ASM representation, value
Doctype, html , dth , 3000h
doc_attributes, htmllang, dth + lang#, 3200h
doc_attributes, htmlmanifest, dth + manifest(), 3100h
Mediatype, img , mi , 5000h
Mediatype, music , mu , 6000h
Mediatype, video , mv , 7000h

html_content, head , hh , 30f0h
head_attributes, , hha , 30e0h
html_content, body , hb , 30d0h
body_attributes, onafterprint , hbap , 30c0h
body_attributes, onbeforeprint , hbbp , 30b0h
body_attributes, onbeforeunload , hbul , 30a0h
body_element, article , hbea , 30afh
body_element, section , hbes , 30aeh
body_element, nav, hben , 30adh
[...]

You can also use a lattice to represent values that are "unlocked" to quickly output said HTML/CSS values in a codex. You recall old video games that use matrix master passwords, that if the correct AND OR if condition met, it would return said gate or value for the main loop:
e.g.: https://i1.ytimg.com/vi/kE4aJwDhQ94/hqdefault.jpg
0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0

Sample `elements` in doctype->html being used:
3 0 0 7 2 0 0 3
0 7 8 0 3 0 5 0
9 0 0 8 0 2 0 2
3 0 5 0 0 0 3 0
0 1 7 0 0 4 0 0
0 6 0 0 5 0 0 9
5 4 0 0 0 4 0 3
0 1 7 0 0 2 0 0

There are many ways you can re-represenmt the values, and quickly call on the addresses that call the render types for the DOM.

-----
Also, for anyone here, please ignore W3C. They are asshats. WHATWG is doing proper standardizations since '04.