3 ms·
> the accessibility you handwaved away, as well as things like adblocking, user-styling, caching, and every other unenumerable concern of endpoints. You are sp
by iLoch 10y ago
> the accessibility you handwaved away, as well as things like adblocking, user-styling, caching, and every other unenumerable concern of endpoints.
You are speaking of things that can and should be addressed with APIs provided by the browser.
- mindslight 10y agoAre you thinking this API would be extension-facing, or page-facing? For the former, then the browser still needs to be able to understand the page to implement this API functionality. Turing-completeness is incompatible with this understanding. For the latter, then that requires page authors to explicitly opt-in to those mechanisms. Obviously they won't do this when incentives are opposed (eg ad blocking). And even in the cooperative case, would require pages to anticipate all features viewers would require.