Just for the record, since I got curious and I saw no mention in the intent email:
I've noticed that this may be used pretty easily for UA detection. So far [1] is the only remotely related thing I've found from a search on Google and GitHub (outside of the firefox codebase ofc). I suspect keeping it exposed may cause more compat issues than removing it, and given finding _something_ was super hard I suspect this is pretty safe to remove, but if someone wants to take a closer look, that'd also be great, I guess. It'd have been great to have a counter on how many times the property is accessed from a content doc or something, but I guess it may not be totally representative, I've seen too much code iterating over the window properties... :P Anyway, great to remove another non-standard feature from content documents :) -- Emilio [1]: http://forums.mozillazine.org/viewtopic.php?f=25&t=232754 On 09/12/2017 09:32 PM, Boris Zbarsky wrote: > Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=864845 > > window.content is a Gecko-specific thing that basically acts like > window.top in untrusted code. In chrome it returns the currently > selected tab, effectively. > > I would like to unship window.content for 57; no one else implements it. > > -Boris > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
