my 2c: View-source has a well defined meaning at this point; if a button says view-source, I expect the (static/server-response) source, not the document outerHTML. If what you really want is a snapshot of the markup *now*, you look for DOM inspector / inspect element function instead. View-source gets you in at the ground floor, and you can navigate from there to the page's resources. It may not end up being that useful for a page like Calendar/index.html, maybe there's a UI solution to toggle between inspector and view-source.
On Tue, Sep 29, 2015 at 10:51 AM, Gareth Aye <[email protected]> wrote: > Hey fxos people, > > *Background* > > Calendar (like many gaia apps) is a single page application. We still use > urls internally for navigation and that came up recently for 2.5 view > source since our client-only urls (/month, /week, /event/add, etc) were > confusing view source which wanted to map urls to html files. > > My question is about the usefulness of view source if it grabs a static > html file instead of a dump of the active html. Calendar's html file lacks > a lot of components which are lazily loaded. I don't use view source > typically (usually I inspect element). Is view source (over inspect > element) a popular desktop feature and what do developers use it for? Are > we okay with the fact that our apps' html files (and probably a significant > overall percentage of mobile web apps) will lack a lot of ui components > which are dynamically loaded? > > (Entirely possible that I am missing something, so don't hesitate to tell > me if my premises are totally off.) > > Thanks, > Gareth > > _______________________________________________ > dev-fxos mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-fxos > >
_______________________________________________ dev-fxos mailing list [email protected] https://lists.mozilla.org/listinfo/dev-fxos
