Closed Bug 817981 Opened 12 years ago Closed 12 years ago

object with type text/html and empty data (<object type="text/html"></object>) prompts user to install missing plugin

Categories

(Core Graveyard :: Plug-ins, defect)

Product:
Core Graveyard
Component:
Plug-ins
Version:
17 Branch
Platform:
x86_64
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 810494

People

(Reporter: aron.cederholm, Unassigned)

Details

Attachments

(1 file)

Reporter's testcase
148 bytes, text/html
Details 
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20100101 Firefox/17.0
Build ID: 20121201125707

Steps to reproduce:

Bug 781394 and Bug 784185 was not resolved on my site. I narrowed down the issue to the following simple html code, which will reproduce in Firefox 17.0.1 on linux x86_64.

<!DOCTYPE html>
<html>
	<head>
		<title>Bug</title>
	</head>
	<body>
		<object type="text/html" data="" id="test"></object>
	</body>
</html>

The same happens without any data attribute at all:
<object type="text/html" id="test"></object>

However specifying an empty protocol, a white space or any other url that will surely 404 will work as expected (I.e. not throwing the user an invalid warning about a missing plugin):
<object type="text/html" data="http://" id="test"></object>
<object type="text/html" data=" " id="test"></object>
<object type="text/html" data="gopher://" id="test"></object>



Actual results:

An alert bar appeared on the top of the page stating: "Additional plugins are required to display all the media on this page." Clicking the "install missing plugins" buttons rendered a popup stating that "No suitable plugins were found".

When the data attribute was specified as data="http://" the alert bar did not show up.


Expected results:

The alert bar should not display for <object type="text/html"> when data is empty or missing.
Component: Untriaged → Plug-ins
Product: Firefox → Core
Attached file Reporter's testcase — 

    
    

    
  
I'm not able to reproduce it in Firefox 20:

m-c
bad=2012-08-07
good=2012-08-08
http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=1bbc0b65dffb&tochange=e55638d4037a

I guess it's fixed by bug 745030. Anyway I don't understand why it's not fixed in FF17 even though bug 745030 landed in FF17.
Status: UNCONFIRMED → NEW
Ever confirmed: true

    
    

    
  
This was fixed in bug 810494, which missed the FF17 merge by a few days :(
It should be fixed in beta/aurora (FF18+) as well as the next FF17 ESR release.

(In reply to Loic from comment #2)
> I'm not able to reproduce it in Firefox 20:
> 
> m-c
> bad=2012-08-07
> good=2012-08-08
> http://hg.mozilla.org/mozilla-central/
> pushloghtml?fromchange=1bbc0b65dffb&tochange=e55638d4037a
> 
> I guess it's fixed by bug 745030. Anyway I don't understand why it's not
> fixed in FF17 even though bug 745030 landed in FF17.

745030 had many followups, it's likely that this regressed again at some point. I'll add a note that we need to add a testcase on 810494
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE

    
  
Product: Core → Core Graveyard

          You need to log in
          before you can comment on or make changes to this bug.
        






  

    
  







  

    

      
Attachment

      

      
      
      
      
    

    

      

        

          

            
General

            

              Creator: 



            

            
Created: 

            
Updated: 

            
Size: