bfgeek

6 ms·

31.
by bfgeek 3y ago
Chromium is currently trying to partition-visited links to prevent this type of history leakage - see: https://groups.google.com/a/chromium.org/g/blink-dev/c/h7Ahp...
32.
by bfgeek 3y ago
Writing negative replies on bugs like this isn't constructive (like #c89). Browser engineers have an extremely difficult job. The codebase is incredibly complex (they aren't just copying data from one system to another - it takes
33.
by bfgeek 3y ago
The issue with this approach is that it would encode all the bugs and quirks into the specification which isn't a good idea. (I'm an engineer on Blink's layout engine). We've recently finished re-architecting Blink'
34.
by bfgeek 4y ago
With this API this would be: .target { anchor-name: --myname; } .tooltip { left: anchor(--myname left); bottom: calc(anchor(--myname top) - 20px); } https://jsfiddle.net/3rasnhyp/
35.
by bfgeek 4y ago
FWIW the equivalent code with this API is: .BlueSquare { width: 100px; height: 100px; top: 0px; left: 0px; anchor-name: --BlueSquare; } .RedSquare { width: 100px; height: 100px; top: calc(anchor(--Bl
36.
by bfgeek 4y ago
One important aspect the work Igalia/Fred/etc did here was defining how MathML should render in browsers. Previously was this undefined[1], and working through all the integration points with CSS/HTML in the new MathML Core s
37.
by bfgeek 4y ago
A lot of folks think that Knuth-Plass is the optimal solution for good looking text, for all text. It really only considers Latin, and even then has restrictions. Some fonts have the space character in the kerning table, and possibly (altho
38.
by bfgeek 4y ago
One interesting/fun problem with text layout is that: width(A) + width(B) != width(A+B) ...which some basic text layout engines assume. The post touches on this, and is one reason why line-breaking is so difficult. If you add so
39.
by bfgeek 5y ago
div { width:100px; height:100px; aspect-ratio: 3 / 2; } This is all well specified and doesn't "break" the box-model in anyway. Anytime there is a definite width/height specified the box well
40.
by bfgeek 6y ago
Will do - we'll make some noise when ready. - Ian
41.
by bfgeek 6y ago
We are in the process of revamping our table layout code at the moment - this should remove subpixel issues like this. Our master bug for these subpixel issues is: https://bugs.chromium.org/p/chromium/issues/d
42.
by bfgeek 6y ago
https://docs.google.com/document/d/17GuApb1fG3Bn0_DVgDQgrtnd... (preview link might be more useful).
43.
by bfgeek 7y ago
Chrome/Blink is in the middle of rolling out a large layout engine change. Chrome 76 behaves more like Safari, Chrome 77 behaves as the article describes. People also might be (1% prob.) placed into a "holdback" experiment gr
44.
by bfgeek 9y ago
There are a few extra performance tricks we can do behind the scenes here. - Chrome's implementation won't actually perform a raster at this stage, instead we'll raster later on a background thread. toDataUrl, etc will raster
45.
by bfgeek 9y ago
We made a mistake in the article there. (There aren't any security issues with pixel read-back here) I'll ping Surma on Monday to get it fixed. The primary reason we did this is to ensure there wasn't a performance cliff if y
46.
by bfgeek 10y ago
Depends on what you are counting as the "same". Edge put together a really great visualization of the API surface of all the browsers. - https://developer.microsoft.com/en-us/microsoft-edge/platfor... Th
47.
by bfgeek 11y ago
Most things should be within the same ballpark. The trouble is at the moment that CSS polyfills are an order of magnitude (or two) off native performance. Example: Current CSS layout polyfills (like grid, regions etc) suffer from this. Wher
48.
by bfgeek 12y ago
If you want a cool way of adding traceur to a development webpage... without adding a compile step, check out https://github.com/bfgeek/swes6 It uses a serviceworker in the background to transpile es6-js requests into
49.
by bfgeek 14y ago
Sort of. There is an endless array of divs which is absolutely positioned, ie: <div id="container" style="top: -2920px">  </div> The actual scrolling is performed by a 'dummy' div, has