Closed
Bug 1182391
Opened 11 years ago
Closed 10 years ago
Support embed a src of a regular page
Categories
(Core Graveyard :: Plug-ins, enhancement)
Core Graveyard
Plug-ins
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1237963
People
(Reporter: dindog, Unassigned)
Details
Firefox don't support embed an regular page, which IE and Chrome is fine, though it's not stated in the spec, like
<embed src="http://bing.com" height="450" width="600">
I've met page uses embed like this to embed a video, Firefox is the only browser I'd tried fail to play.
Even Firefox decided not to support it, the error message should not be "A plugin is needed to display this content"
Comment 1•10 years ago
|
||
@Reporter, this appears fixed for a future release. However please send detailed steps so that ensure I have captured your request.
Please include your operating system. [Windows, Linux, Macintosh]
Please include your Firefox version number.
Thanks,
Version 46.0a1
Build ID 20160104030217
User Agent Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:46.0) Gecko/20100101 Firefox/46.0
Flags: needinfo?(dindog)
(In reply to Michelle Funches - QA from comment #1)
> @Reporter, this appears fixed for a future release. However please send
> detailed steps so that ensure I have captured your request.
> Please include your operating system. [Windows, Linux, Macintosh]
> Please include your Firefox version number.
>
> Thanks,
> Version 46.0a1
> Build ID 20160104030217
> User Agent Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:46.0)
> Gecko/20100101 Firefox/46.0
Name Firefox
Version 43.0.3
Build ID 20151223140742
Update Channel release
User Agent Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101 Firefox/43.0
I can reproduce this bug using a simple html file:
<html>
<head></head>
<body>
<embed src="http://bing.com/" height="450" width="600">
</body>
</html>
You can tell the difference openning it with Chrome and Firefox
Flags: needinfo?(dindog)
And for one correction, IE 8 didn't support it too, it seems IE has accepted it through common practice.
Comment 5•10 years ago
|
||
Supporting these seems to contradict the HTML spec, which only allows treating an <embed> as a subframe (like <iframe> or <object>) if the content type is "image/svg+xml". Since that clearly doesn't apply in this case, we are following the spec.
https://html.spec.whatwg.org/multipage/embedded-content.html#the-embed-element
dindog, is there a reason why you're using <embed> for this instead of the standard <iframe> or <object>? <embed> is specifically for plugins and really should not be used in this case.
dbaron, do you think that it's worth asking about the implementation discrepancy on the whatwg list? I'm inclined to WONTFIX this bug unless there's evidence that this is actually breaking sites in the wild, in which case we should get the spec fixed.
Flags: needinfo?(dbaron)
Updated•10 years ago
|
Flags: needinfo?(dindog)
It's a report in comminity, from where I knew about this bug. Pages in wild use it. Maybe that's why IE didn't support it originally in IE 8 does now.
Again, even Firefox decides not to support it , the error message still should be change to something more accurately instead of telling users they didn't have the proper plugins
Flags: needinfo?(dindog)
(In reply to Benjamin Smedberg [:bsmedberg] from comment #5)
> Supporting these seems to contradict the HTML spec, which only allows
> treating an <embed> as a subframe (like <iframe> or <object>) if the content
> type is "image/svg+xml". Since that clearly doesn't apply in this case, we
> are following the spec.
>
> https://html.spec.whatwg.org/multipage/embedded-content.html#the-embed-
> element
>
> dindog, is there a reason why you're using <embed> for this instead of the
> standard <iframe> or <object>? <embed> is specifically for plugins and
> really should not be used in this case.
>
> dbaron, do you think that it's worth asking about the implementation
> discrepancy on the whatwg list? I'm inclined to WONTFIX this bug unless
> there's evidence that this is actually breaking sites in the wild, in which
> case we should get the spec fixed.
I read the spec's link briefly, it doesn't say ONLY "image/svg+xml" is allowed, it says how to treat "image/svg+xml" when it's determined.
>The embed element has no fallback content.
>If the user agent can't find a suitable plugin when attempting to find and instantiate one for the algorithm above,
>then the user agent must use a default plugin.
>This default could be as simple as saying "Unsupported Format".
Does Chrome and IE take that "default plugin" as standard "text/HTML" for one more try?
Comment 8•10 years ago
|
||
The fact that other webmakers and other browsers deviate substantially from the W3C HTML standard has happened in the past, and only in extremely rare cases did Gecko forgo the norm to align with the deviation. In such rare cases, the Gecko representatives at the W3C did their best to make the current deviation the new norm.
The way to include a third-party web page as part of a web page is <iframe> (specific) or <object> (general), not <embed> and not <img>. One of the reasons why serious professional users rely on Firefox is that Firefox is known to adhere to well-known standards which are not going to change at the whim of a proprietary browser's CEO desiring customer lock-in. The same could historically not be said of, for instance, Microsoft.
IMHO the burden of the proof lies with whoever pretends that this deviation from the norm is "common practice".
Severity: normal → enhancement
OS: Unspecified → All
Hardware: Unspecified → All
Version: unspecified → Trunk
Comment 9•10 years ago
|
||
Bug 1237963 fixed this. Given that this affects web compatibility, we should propose a spec change.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
Comment 10•10 years ago
|
||
The spec bug for this is already filed: https://github.com/whatwg/html/issues/513
comment 9 and comment 10 sounds like the correct solution
Flags: needinfo?(dbaron)
Updated•4 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•