132384 - Titlebar doesn't disappear when fullscreen enabled on window.open

Status: RESOLVED DUPLICATE of bug 116503

(Core :: DOM: Core & HTML, defect)

Description

[Matthew Schultz]

The titlebar doesn't disappear like it does in MSIE when fullscreen is enabled
on a window.open command in Javascript.  Even when I set titlebar=no, the
titlebar still does not disappear.  I setup a small test at the url listed.

Comment 1

[Phil Schwartau]

Confirming report using Mozilla trunk 20020317xx WinNT, Linux.
OS: Win98 ---> All.

Browser, not engine. Reassigning to danm for further triage -

Comment 2

[Boris Zbarsky [:bzbarsky]]

The way to get fullscreen is to do:

foo.fullScreen = true;

where foo is the window handle (though that has been disabled for security
reasons).  I don't believe we support "fullscreen=yes"

Comment 3

[Matthew Schultz]

The support for fullscreen=yes does exist when all other attributes are not 
specified when opening a window.  The titlebar doesn't disappear as well though 
like it does in MSIE.  Does the W3 mention anything about how fullscreen should 
behave?

Comment 4

[Boris Zbarsky [:bzbarsky]]

window.open is not defined in any W3C specification, so no.

Comment 5

[Matthew Schultz]

So is there going to be support for fullscreen without the titlebar?  Seems 
kind of strange if you ask me to implement fullscreen only partially like 
MSIE.  There would be better compatibility with sites supporting fullscreen 
that were designed around MSIE.

Comment 6

[bora123]

This was working before then somebody came out and said that this should be
considered as a bug. Without further examination, this was considered as a bug
and the permissions preferences file was altered to not to open windows from
script in full screen. Some people has mighty and God like powers over the
decisions. Decisions made by individual preferences and thoughts which are
unfortunately accepted often in mozilla tree. These are itsy bitsy details, but
you should consider what others might have use of from these details. Of course,
the motive was 'full screen window attack' for banning this feature from Mozilla
which would have been solved in a more user friendly manner (like another check
box into preferences->advenced->scripts & windows) than just completely
disabling it from hard coded permissions file.

regards

Comment 7

[Boris Zbarsky [:bzbarsky]]

All of which has nothing to do with _this_ bug, that I can see....

Comment 8

[bora123]

Let me refresh your memory, open the file

D:\Program Files\mozilla.org\Mozilla\defaults\pref\all.js

go to line 300, the policy set on line 300 is

pref("capability.policy.default.Window.fullScreen", "noAccess");

Comment 9

[Boris Zbarsky [:bzbarsky]]

Yeah.  Except this bug is about the fullscreen=yes option to window.open(), not
about window.fullScreen.

Comment 10

[Matthew Schultz]

My bad, you're right, fullscreen=yes doesn't work at all in Mozilla.  In
Netscape, you get fullscreen with a titlebar and in MSIE, you get fullscreen
without a titlebar.  

Comment 11

[bora123]

>Yeah.  Except this bug is about the fullscreen=yes option to window.open(), not
>about window.fullScreen.

Yeah! And arent they related to each other in anyway? If there is no way of
scripting up a window to fullscreen in mozilla, what is the meaning of keeping
this bug from being tagged as not "INVALID"? your message '#2' is about the
'foo.fullScreen = true' which is invalid because it is not working. Although
reporter seems like asking for fullscreen=yes option to be considered, I believe
that he can also accept foo.fullscreen=true; as a second option which gives him
the same functionality. However, it is not working anymore as well. Instead of
diverting what I am trying say to 'you didnt understand this bug, dude'
establisments, may be you would come up with some more constructive arguments. 

Comment 12

[Boris Zbarsky [:bzbarsky]]

> your message '#2' is about the 'foo.fullScreen = true'

Indeed, and I apologize for that.  That was not exactly relevant to this bug.

The difference between fullscreen=yes and 'foo.fullScreen = true' is that the
former allows you to open a window in fullscreen whereas the former allows you
to put any window (even one you don't "own", in that there is session history
and such in it) into fullscreen.  If foo.fullScreen had a check whereby a page
had to window.open() a window before putting it in fullscreen, it could become a
more reasonable (from a security standpoint) option to re-enable it....

Comment 13

[Matthew Schultz]

Yes I can accept window.fullScreen = true; as a workaround and that I wouldn't
need fullscreen=yes but it doesn't give the functionality I'm looking for.  If
you open a window using window.open() in MSIE, it opens a window without the
titlebar.  In fact, it puts it in actual full screen mode.  It's nice to put
things in fullscreen in Mozilla and the window gets bigger but it doesn't
actually go full screen does it?  Everything disappears BUT the titlebar on the
top.  Why would it be a security issue to allow javascript to allow
window.open() to open a new window in actual fullscreen without the titlebar
like MSIE?  

Comment 14

[Juan José Mata]

Changing target milestone to 'Future' since these seem to have missed the 1.2
alpha.  If you are still considering a fix for 1.2 please re-target accordingly.

Comment 15

[Andreas Kunz]

Even if this is implemented, it might not work due to bug 126814:
Opening a new window (when the first window was in fullscreen mode without title
bar) results in a 'almost fullscreen' window that has all the real fullscreen
buttons, but also a title bar above them. -> relation/dependency?

Comment 16

[Gérard Talbot]

This bug has not been active for a long time.
Note that bug 116503 is about fullScreen=yes and that not too long ago, MSIE 6
even started to drop support for fullScreen=yes. 
"The definition of the fullscreen=yes specification [in MSIE 6 SV1] is changed
to mean 'show the window as maximized,' which will keep the title bar, address
bar, and status bar visible." 
More reading on this can be found at:

http://developer-test.mozilla.org/docs/Gecko_DOM_Reference:DOM_window_Reference:window.open%28%29

I am resolving this bug as DUPLICATE of bug 116503.

*** This bug has been marked as a duplicate of 116503 ***