Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon. Entire thread

Why browsers are bloated

Name: Anonymous 2014-07-27 0:20

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?

Name: Cudder !cXCudderUE 2016-03-27 23:27

>>880
Looking at CSS tokeniser+parser. I've set aside box generation and rendering for now since there's no use in doing that without having a way of actually consuming CSS.

There's an odd '||' operator which I can't find anywhere else in the spec:

http://stackoverflow.com/questions/30702971/how-is-the-operator-used-in-css

https://lists.w3.org/Archives/Public/www-style/2013Apr/0059.html

So it's completely fucking useless unless you're a circlejerking academic steeped in that LL/LR/etc. bullshit, and I've carefully read every single word of the CSS3 selectors spec without finding a single mention of it. It only has ~=, |=, ^=, $=, and *=. THANK YOU W3C FOR MAKING STUPID IMPLEMENTATIONS MORE INEFFICIENT! :facepalm:

Newer Posts