Closed Bug 643621 Opened 14 years ago Closed 14 years ago

XHTML5 a target - iframe name problem

Categories

(Core :: Layout: Images, Video, and HTML Frames, defect)

x86
Windows 7
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 488247

People

(Reporter: bugzilla33, Unassigned)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows NT 6.1; rv:2.0) Gecko/20100101 Firefox/4.0
Build Identifier: Mozilla/5.0 (Windows NT 6.1; rv:2.0) Gecko/20100101 Firefox/4.0


a target - iframe name
do not work.

Reproducible: Always

Steps to Reproduce:

1. Open URL
2. Click link to open image in iframe.

Actual Results:  

Image opens in new tab.

Expected Results:  

Image opens in iframe.


Explorer, Chrome, Safari, Opera, Konqueror open image in iframe.
http://dev.w3.org/html5/markup/a.html
"target = browsing-context name"

http://dev.w3.org/html5/markup/iframe.html
"name = browsing-context name"
This is a case in which XHTML1.0 and HTML5 somewhat disagree.  We implement what XHTML1.0 says so far, pending HTML5 stabilizing on the behavior it wants.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
HTML5 + XML = XHTML5
not XHTML1.0

http://en.wikipedia.org/wiki/HTML5
"XHTML5 is the XML serialization of HTML5. XML documents must be served with an XML Internet media type such as application/xhtml+xml or application/xml.[38] XHTML5 requires XML’s strict, well-formed syntax. In XHTML5 the HTML5 doctype html is optional and may simply be omitted."
Summary: a target - iframe name, problem application/xhtml+xml → XHTML5 a target - iframe name problem
I'm well aware of that.  The point is, the spec for what to do with documents of type application/xhtml+xml used to say one thing, now says something slightly different, and is still in flux.
Product: Core → Core Graveyard
Component: Layout: HTML Frames → Layout: Images
Product: Core Graveyard → Core
You need to log in before you can comment on or make changes to this bug.