292105 - Should not allow spaces in window name param of window.open()

Status: RESOLVED EXPIRED

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

Description

[JongAm Park]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050418 Firefox/1.0+
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050418 Firefox/1.0+

With windows.open( [URL string], [window name], [options] );
Mozilla-based web browser allow space in the window name like this.
        
       window name : "My Description"

However, the IE doesn't allow it, and it generates a script error.


Reproducible: Always

Steps to Reproduce:
1. insert an anchor and write its onClick method.
2. onclick="window.open( 'http://www.cnn.com', 'CNN News', ... )
3. See if it works for the Mozilla and the IE

Actual Results:  
script error in the IE

Expected Results:  
make things consistent with the IE and the Mozilla

I dont' know which one is more stanard-bearing. Is space characters allowed in
the standard?

Whatever it is, it would be great if it is consistent with different browsers.
I will be better if there is a visual cue about this problem. ( maybe the
JavaScript debugger, Venkamm, should have the visual cue. )

Comment 1

[Brendan Eich [:brendan]]

Please file DOM level 0 bugs correctly.

I think this is WONTFIX.  Hixie may have spec'ed what should happen here as part
of whatwg.org's web apps specs.

/be

Comment 2

[Hixie (not reading bugmail)]

Not yet, but yeah, that'll eventually happen. I'll note this bug as one of the
things to look at.

Comment 3

[Gérard Talbot]

I believe this is a valid bug: the window name should be a string without blank
space. The window name should be usable as a target of links and forms.
e.g.: <a href="path/file.html" target="CNN News" ...>

The summary as written is too general and not specific.

Comment 4

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 5

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.

Comment 6

[Hixie (not reading bugmail)]

Update: The spec as written today does not restrict custom names (other than saying they can't start with underscores).