- From: Bianca Danforth via GitHub <sysbot+gh@w3.org>
- Date: Mon, 12 Aug 2019 20:57:11 +0000
- To: public-css-archive@w3.org
> For the Fathom use-case, it does seem to make sense. However, can't Fathom be done on the server? In that setting, the page could be rendered in a "viewport" that has the entire document. There are certainly applications that could run on a server, but most of the applications we have encountered thus far would need Fathom to run in the client. For example, we could use Fathom to help password managers better identify login forms, or perhaps we could build a more complete accessibility tree by using Fathom to identify non-semantic HTML elements. We recently built a prototype shopping assistant that uses Fathom to extract product information from e-commerce pages for users to track price changes over time. Also from a privacy perspective, it's much easier to protect user data if we perform all of the work in the client and have little to no server component. -- GitHub Notification of comment by biancadanforth Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4122#issuecomment-520592390 using your GitHub account
Received on Monday, 12 August 2019 20:57:14 UTC