Bugzilla

(In reply to Nika Layzell [:nika] (ni? for response) from comment #11)
> It might be worthwhile to check and see what the consequences of something like this would be.

Out of non-officially supported cases, I think various (don't have numbers, sorry) advanced users load `chrome://browser/content/places/places.xul` in a content tab to avoid having the Library as a separate window. Long term this problem should be solved by Firefox View, but we're not there.

(In reply to Nika Layzell [:nika] (ni? for response) from comment #11)
> It might be worthwhile to check and see what the consequences of something like this would be.

Out of non-officially supported cases, I think various (don't have numbers, sorry) advanced users load `chrome://browser/content/places/places.xhtml` in a content tab to avoid having the Library as a separate window. Long term this problem should be solved by Firefox View, but we're not there.

(In reply to Nika Layzell [:nika] (ni? for response) from comment #11)
> It might be worthwhile to check and see what the consequences of something like this would be.

Out of non-officially supported cases, I think various (don't have numbers, sorry) advanced users load `chrome://browser/content/places/places.xhtml` in a content tab to avoid having the Library as a separate window. They may have a bookmark pointing to that URL. Long term this problem should be solved by Firefox View, but we're not there yet.

(In reply to Nika Layzell [:nika] (ni? for response) from comment #11)
> It might be worthwhile to check and see what the consequences of something like this would be.

Out of officially supported cases, I think various (don't have numbers, sorry) advanced users load `chrome://browser/content/places/places.xhtml` in a content tab to avoid having the Library as a separate window. They may have a bookmark pointing to that URL. Long term this problem should be solved by Firefox View, but we're not there yet.