bokan

5 ms·

1.
by bokan 2y ago
But the probability of life arising is an unknown. Intuitively I too feel it probably isn't that small, but it wouldn't be the first time intuition about the universe is wrong. How do you _know_ the odds of life arising aren'
2.
by bokan 5y ago
Disclaimer: I'm the one who made the change in [1] so I'm biased but... IMHO the argument on the blog mischaracterizes the situation - Chrome didn't break these properties but changed how they're interpreted under pi
3.
by bokan 6y ago
The extension uses a new URL fragment addition that Chrome has shipped: https://github.com/WICG/scroll-to-text-fragment so these links will work on any Chrome/Chromium-based browser. (in non-Chromium browsers with
4.
by bokan 6y ago
The big difference is that the original intended text is encoded in the URL. An element-id fragment is better than just a URL but will often be less granular than the exact text being linked (e.g. a heading). If you're looking to link
5.
by bokan 8y ago
> That said, it seems easy to make this backwards compatible: if the existing #blah syntax is a valid link, that should take precedence. That's indeed how it works. The majority of the compatibility concerns appear to be with apps t
6.
by bokan 8y ago
That's true, but presumably these pages would have the same problem with existing id-fragments, no?
7.
by bokan 8y ago
Thanks, I'll make sure to dig into that some more!
8.
by bokan 8y ago
> Are there any guidelines for chromium development? Absolutely! Launching a change to the web platform is a long, arduous process. This feature is currently taking the very early first steps. For more details, see https://www
9.
by bokan 8y ago
Which is exactly why we build an experiment first, to find potential issues before shipping. If you do see a page that you think might break and you're on Chrome newer than 74.0.3706.0, try turning on chrome://flags#enable-te
10.
by bokan 8y ago
> Would you append the & to the fragment, or to the query? If to the fragment couldn’t that affect routing for SPAs? To the fragment. Tt could, depending on how the app was written. Is there a framework or some common techniques that
11.
by bokan 8y ago
It will. The specification process needs to be informed by implementation and experimentation. When implementing a feature we'll learn all sorts of things and hit bumps that will help guide the design. Once we have a working implement
12.
by bokan 8y ago
The proposal, as currently stated, is to use fragment id processing first. If that fails to find a target, fallback to text matching. In other words, even if you give an element "id='targetText=something'", this feature
13.
by bokan 8y ago
Feature author here. I'd like to first clarify that this is still in the super-early stage of development; none of this is shipped or finalized yet. The feature hasn't even requested approval to ship at which point these kinds of
14.
by bokan 8y ago
What would you hash though? Content on a page changes frequently and dynamically so the hash would mismatch very frequently.
15.
by bokan 8y ago
Feature author here. The CSS timing attack actually influenced the design process heavily. The original design was to use a stripped down CSS selector but we found this too large of an attack surface. There's definitely still concerns
16.
by bokan 8y ago
That depends on the author annotating their page with ids so it's highly content dependent. In addition, authors can't always predict what will be interesting to users and pages frequently don't have IDs on elements you might
17.
by bokan 8y ago
If this is true (I don't know either way, I've only followed this casually), why go through the whole dog and pony show in the first place? In that case, Amazon seems to have shot themselves in the foot here by playing a carnival
18.
by bokan 9y ago
> which means that layout performance affects what looks like script time Chrome's profiler actually shows synchronous layouts and style recals forced from JS as layout/style so it's not misleading in that way. The traces
19.
by bokan 9y ago
The question isn't whether you should or shouldn't try to improve, it's where to invest your resources. Servo improves the speed of layout, style, etc. but is that really what's making the web experience slow? If you do
20.
by bokan 10y ago
This should no longer be the case, at least for Safari, Edge, and Chrome. All of these "detach" fixed/stick position elements from the viewport once you start zooming.