Closed Bug 644540 Opened 13 years ago Closed 13 years ago

EMC Powerlink's My Support doesn't load using Firefox 4's HTML 5 parser (powerlink.emc.com)

Categories

(Tech Evangelism Graveyard :: English US, defect)

Product:
Tech Evangelism Graveyard
Component:
English US
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: luis.prieto, Unassigned)

References

(
URL
)

Details

(Keywords: regression, Whiteboard: [HTML5])

Attachments

(3 files)

Err1
218.04 KB, text/plain
Details
Err2
15.96 KB, text/plain
Details
Search function to reproduce the issue
17.34 KB, image/png
Details 
User-Agent:       Mozilla/5.0 (Windows NT 5.1; rv:2.0) Gecko/20100101 Firefox/4.0
Build Identifier: Mozilla/5.0 (Windows NT 5.1; rv:2.0) Gecko/20100101 Firefox/4.0

When I click on "My Support" on EMC Powerlink's website, it keeps loading and does not finish.

Reproducible: Always

Steps to Reproduce:
1.Enter powerlink.emc.com
2.Navigate/select Support/My Suppport

Actual Results:  
It keeps loading.

Expected Results:  
"My Suppot" loaded.
You need an account to enter EMC Powerlink.
(In reply to comment #2)
> Does this still happen with a clean new profile?
> http://support.mozilla.com/en-US/kb/Managing%20profiles
> 
> Or in Safe Mode?
> http://support.mozilla.com/en-US/kb/Safe%20Mode

Yes, I'm afraid it still happens.
Could you see if there are any errors in the console (just errors, don't need to warnings) and paste them here please. Use Ctrl + Shift + J to access.

Does it work ok in 3.6.x?
Version: unspecified → Trunk
Yes, there are a lot of warnings and a some errors:

Error: uncaught exception: Error: Backbase Exception #12

Error: bb is null
Archivo de origen: https://powerlink.emc.com/nsepn/webapps/btg548664833igtcuup4826/staticKmSearchResources/KM-3_20-20100423-112230-528/Backbase/engine/core.js
Línea: 1 (a lot of that)

Error: entidad no definida
Archivo de origen: https://powerlink.emc.com/nsepn/webapps/btg548664833igtcuup4826/mysupport/index.jsf?href=registeredView.jsp|dest=_idJsp5|mode=appendChild|xi=true
Línea: 11, columna: 32
Código fuente:
    <span>My Support for</span>&nbsp;

Error: uncaught exception: Error: Backbase Exception #12

(In reply to comment #4)
> Could you see if there are any errors in the console (just errors, don't need
> to warnings) and paste them here please. Use Ctrl + Shift + J to access.
> 
> Does it work ok in 3.6.x?
Reporter, please can you confirm whether this issue still occurs using Firefox 4.0.1 (http://www.mozilla.com/firefox/new/) or higher, in Firefox safe mode (http://support.mozilla.com/kb/Safe+Mode) and/or with a clean profile (http://support.mozilla.com/kb/Basic+Troubleshooting#w_8-make-a-new-profile). Ideally, also check using the latest nightly: http://nightly.mozilla.org/

If this issue no longer occurs, please close as "Resolved Worksforme".

It it in fact still occurs, please provide as much extra information as possible, including what versions tried, whether safe mode/new profile tested etc. Thanks! :-)
Attached file Err1 — 

    
    

    
  

      
      
      
      

        Attached file
          
        Err2
        — 
      

    


  

    
    

    
  
Hello,

In FF 3.6 it worked fine.

In FF 4.0.1 it still happens. In consose the following messages appear:

Error: uncaught exception: Error: Backbase Exception #12

Error: bb is null
Archivo de origen: https://powerlink.emc.com/nsepn/webapps/btg548664833igtcuup4826/staticKmSearchResources/KM-3_20-20100423-112230-528/Backbase/engine/core.js
Línea: 1 (8 times)
And if I click on the source code, attached file Err1.txt appears.

Error: entidad no definida
Archivo de origen: https://powerlink.emc.com/nsepn/webapps/btg548664833igtcuup4826/mysupport/index.jsf?href=registeredView.jsp|dest=_idJsp5|mode=appendChild|xi=true
Línea: 11, columna: 32	
Código fuente:	
    <span>My Support for</span>&nbsp;
And if I click on the source code, attached file Err2.txt appears.

And finally:
Error: uncaught exception: Error: Backbase Exception #12

    
    

    
  
Thanks for the update.

The easiest way to try and narrow this down (seeing as I don't have a login for it), might be to find the regression range, if you had a chance at some point? If so, please check out this tool (will take 20-30 mins):
http://harthur.github.com/mozregression/

Thanks!

    
    

    
  
You can register for free.

    
    

    
  
I've just created an account and the URL in the URL field for this bug returns an access denied error.

If I go directly to powerlink.emc.com; I only see a "Support" dropdown, with no mention of a "My Support" sub-entry. I tried clicking on "Support", and the resultant page loaded fine.

I suspect I'm not able to access the page needed, with my free account.

Before having to resort to finding a regression range using the tool in comment 10, please can you try:
- Going to about:config
- Entering "html5.parser.enable" in the filter box (without quotes)
- Changing it's value to false
- Retrying the page in question and seeing if it helped
- Afterwards, resetting html5.parser.enable back to true

    
    

    
  
Setting "html5.parse.enable" to false seems to solve the problem! What now?

    
    

    
  
It means that the site no longer works under Firefox 4's new HTML5 parser. It's therefore very likely that there is an error in the site's HTML markup that is causing the problem; but will need to leave it to someone more knowledgeable than myself to diagnose further.

Moving to Core::HTML Parser for visibility; until otherwise proven tech evangelism (ie the site's fault).
Blocks: html5-parsing
Status: UNCONFIRMED → NEW
Component: General → HTML: Parser
Ever confirmed: true
Keywords: regression
Product: Firefox → Core
QA Contact: general → parser
Summary: EMC Powerlink's My Support doesn't load → EMC Powerlink's My Support doesn't load using Firefox 4's HTML 5 parser
Whiteboard: [likely Tech Evang but needs confirmation]
Version: Trunk → unspecified

    
    

    
  
Oh and meant to say thanks for the bug report! :-)

    
    

    
  
Thanks to you guys.

    
  
Assignee: nobody → english-us
Component: HTML: Parser → English US
Product: Core → Tech Evangelism
QA Contact: parser → english-us
Whiteboard: [likely Tech Evang but needs confirmation]

    
    

    
  
Anthony, have you been able to test that it's not an actual (albeit unlikely) regression caused by the new parser? I intentionally didn't move to TE yet for that reason (comment 14).
Assignee: english-us → nobody
Component: English US → HTML: Parser
Product: Tech Evangelism → Core
QA Contact: english-us → parser
Whiteboard: [likely Tech Evang but needs confirmation]

    
    

    
  
I was unable to identify a regression window.  Based on what I read I thought it was an obvious TE bug.  Frankly, I'm not prepared to give my personal information to this site just to test this "edge case".  I'll leave it to yourself or Luis to determine the regression range.

To easily find a regression range, please use the following tool:
http://harthur.github.com/mozregression/

    
    

    
  
Anthony a regression range isn't needed, please see comments 12-14.

    
    

    
  
(In reply to comment #19)
> Anthony a regression range isn't needed, please see comments 12-14.

Ok, then what is needed to prove this is a TE bug?

By the way, simplifying the whiteboard tag...
Whiteboard: [likely Tech Evang but needs confirmation] → [tech-evang?]

    
    

    
  
(In reply to comment #0)
> Steps to Reproduce:
> 1.Enter powerlink.emc.com
> 2.Navigate/select Support/My Suppport

I registered an evaluation account, but I don't see an option "My Support" under the "Support" menu. Do you mean you see an item called "My Support" under the "Support" menu?

(In reply to comment #20)
> (In reply to comment #19)
> > Anthony a regression range isn't needed, please see comments 12-14.
> 
> Ok, then what is needed to prove this is a TE bug?

An analysis of why exactly this fails and if that behavior is by design. Alternatively, if this turns out to be too deep in the dark matter land, we might kick this over to evang without analysis, but let's try to find out what's going on here first.

    
    

    
  
I have checked and I'm afraid that I can't reproduce the bug with a free account (it hasn't a "My Support" item)

    
    

    
  
(In reply to comment #22)
> I have checked and I'm afraid that I can't reproduce the bug with a free
> account (it hasn't a "My Support" item)

OK. Unless you can debug this further yourself, I suggest that you contact EMC and point them to this bug.
Assignee: nobody → english-us
Component: HTML: Parser → English US
Product: Core → Tech Evangelism
QA Contact: parser → english-us
Whiteboard: [tech-evang?]

    
    

    
  
I've just told them.

Regards.

    
    

    
  
(In reply to comment #22)
> I have checked and I'm afraid that I can't reproduce the bug with a free
> account (it hasn't a "My Support" item)

This is not entirely true, the bug also applies to the "Search" function, which should be available in a free account.

    
    

    
  
I'm seeing the same issue as I was "forced" to upgrade to FF5 from 3.6.x.  If you want me to try the regression test I might be able to do it

    
    

    
  
Regression testing not needed, EMC confirmed to me that they're working on it.

    
    

    
  
(In reply to comment #27)
> Regression testing not needed, EMC confirmed to me that they're working on
> it.

Based on this comment, I think this is not a Firefox bug.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → INVALID

    
    

    
  
Since this was a problem on EMC's end, and the bug lives in TE, let's leave it open until EMC confirms a fix.
Status: RESOLVED → REOPENED
Resolution: INVALID → ---

    
    

    
  
Good idea, Chris, EMC wrote to me:

>We have indeed had reports of some compatibility problems with Firefox 4.  Our >development team is investigating this and determined that one of the component >software elements is triggering this problem.  We are working with the vendor to >identify and implement a permanent fix.

Maybe there will be some feedback, on what's broken.

I've seen other pages broken with html5 parser too btw.; e.g. VMware Partner Central, MSP Center Helpdesk - I'm afraid I don't have to knowledge and time to investigate into these.

    
  
Summary: EMC Powerlink's My Support doesn't load using Firefox 4's HTML 5 parser → EMC Powerlink's My Support doesn't load using Firefox 4's HTML 5 parser (powerlink.emc.com)
Whiteboard: [HTML5]

    
    

    
  
(In reply to j.j. from comment #32)
> http://twitter.com/#!/EMCsupport/status/88367598944788480

Given that the parser changes first appeared in a Firefox beta (Firefox 3.7 Alpha 5) on 16th June 2010, that is quite frankly ridiculous.

    
    

    
  
With fix in comment 13 all seems to find. Any news from EMC?

    
    

    
  
(In reply to Marijus Ravickas from comment #35)
> With fix in comment 13 all seems to find. Any news from EMC?

This workaround does not work anymore with recent firefox nightly builds.

    
    

    
  
This workaround also break's up CA Service Desk web interface functionality.

    
    

    
  
(In reply to Marijus Ravickas from comment #35)
> With fix in comment 13 all seems to find.

This is NOT a fix at all. Disabling the HTML 5 parser reanimates hundreds of old parsing an layout bugs.

    
    

    
  
(In reply to Marijus Ravickas from comment #35)
> Any news from EMC?

EMC is not involved here, AFAICT. 
Please push them and point to this bug.

    
    

    
  
This problem still exists on Firefox 5 and disabling html5 parsing seems to "fix" it. EMC web support I spoke to said that IE's html5 works and it seems to be Firefox's implementation that is broken.

    
    

    
  
(In reply to Jason Johns from comment #40)
> EMC web support I spoke to said that IE's html5 works and it seems
> to be Firefox's implementation that is broken.

Well, they should attach a testcase *here* in this bug report.
It's not reproducible with a free account (see comment 21 and 22).

BTW, does it work in recent builds of Opera or Google Chrome? That's usually more significant than IE's support.
Status: REOPENED → NEW

    
    

    
  
(In reply to j.j. from comment #41)
> (In reply to Jason Johns from comment #40)
> > EMC web support I spoke to said that IE's html5 works and it seems
> > to be Firefox's implementation that is broken.
> 
> Well, they should attach a testcase *here* in this bug report.
> It's not reproducible with a free account (see comment 21 and 22).
> 

Does free account has search functionality (Search Powerlink/Search Support tabs on the home page)? If yes, the bug is perfectly reproducible here - search results are never loaded.

> BTW, does it work in recent builds of Opera or Google Chrome? That's usually
> more significant than IE's support.

It does work with chromium 12 and 14 if it is of any significance (chromium build 14.0.835.94).

    
    

    
  
(In reply to j.j. from comment #41)
> (In reply to Jason Johns from comment #40)
> BTW, does it work in recent builds of Opera or Google Chrome? That's usually
> more significant than IE's support.

Yes, it does work with both (tested under Windows).

    
    

    
  
Updating to Firefox 6 does not correct this issue. Disabling html5 still works around the issue.

    
    

    
  
(In reply to Andrey Borzenkov from comment #36)
> (In reply to Marijus Ravickas from comment #35)
> > With fix in comment 13 all seems to find. Any news from EMC?
> 
> This workaround does not work anymore with recent firefox nightly builds.

This means that the problem relates to fragment parsing (either innerHTML setter or createContextualFragment). See http://hsivonen.iki.fi/old-fragment/

Could someone who can reproduce this, please, take a look at the script sources to see if the site assigns "<script>...</script>" to the innerHTML of a node that's not in the document at the time the innerHTML setter is called? (Also worth searching script sources for the string "Text for stupid IE".)

    
    

    
  
So with the help of additional data forwarded to me via email, I took a look at this again. I still can't access the parts of the EMC portal that are reported to be buggy. However, I searched through the scripts that are linked to the parts of the site that I get to see and that I believe to get included on the problematic pages (according to the data forwarded to me).

Instances of setting innerHTML look innocent except for the one case in HM_ScriptDOM.js that is so minified that I have no idea what actually gets passed to the innerHTML setter in the actual problem situation (or if that innerHTML ends up running in Firefox at all).

I think it would be worthwhile if someone who can reproduce the problem did so with the script tab of Firebug open and then used the search box in Firebug to search for innerHTML to see if something comes up where a script tag is assigned to innerHTML.

That the portal works in IE or Chrome doesn't prove anything. It seems that their JS code has accumulated ad hoc browser sniffing patch over patch since the Netscape 4.x and IE4 days. It's quite possible that they end up running different code in Firefox, IE and Chrome.

    
    

    
  
So I am able to get to that section and I found a bunch of references to innerHTML but not being a developer I don't know exactly what I'm looking for.   I found it in a couple of places.  

cascade_css.js - if(typeof(loc)=="undefined"||loc==""){var loc="";if(document.body&&document.body.innerHTML){var tt=document.body.innerHTML.toLowerCase();var last=tt.indexOf("cascade.js\"");if(last>0){var first=tt.lastIndexOf("\"",last);if(first>0&&first<last)loc=document.body.innerHTML.substr(first+1,last-first-1);}}}

core.js - There's a few references in there but truthfully I don't know what is what.  I can copy and paste the whole thing into a file and upload it but I don't know if that would do any good.

HM_ScriptDOM.js - Looks to be what Henri mentioned and very minimal: jp.innerHTML=el.qk


One thing to note.  This also occurs on the front page under "powerlink quick start" and found this on the script tab:  
eDIV.innerHTML = banner; 
and 
document.getElementById("noNumberEntered").innerHTML = "";  

The rest of the references seem to be commented out and they all have to do with the service request pane.

    
    

    
  
(In reply to Paul Benish from comment #47)
> So I am able to get to that section and I found a bunch of references to
> innerHTML but not being a developer I don't know exactly what I'm looking
> for.   I found it in a couple of places.  

Thank you.

> cascade_css.js - if(typeof(loc)=="undefined"||loc==""){var
> loc="";if(document.body&&document.body.innerHTML){var
> tt=document.body.innerHTML.toLowerCase();var
> last=tt.indexOf("cascade.js\"");if(last>0){var
> first=tt.lastIndexOf("\"",last);if(first>0&&first<last)loc=document.body.
> innerHTML.substr(first+1,last-first-1);}}}

That bit reads innerHTML without assigning to it, so it shouldn't be the cause of the problem.

> core.js - There's a few references in there but truthfully I don't know what
> is what.  I can copy and paste the whole thing into a file and upload it but
> I don't know if that would do any good.

That's a file that I didn't see yesterday, so I'd be interested in learning how it uses innerHTML. Could you send me the URL to core.js, please?

> One thing to note.  This also occurs on the front page under "powerlink
> quick start" and found this on the script tab:  
> eDIV.innerHTML = banner; 
> and 
> document.getElementById("noNumberEntered").innerHTML = "";  

I tried to eyeball through all the possible values that |banner| can get, and they all looked benign.

    
    

    
  
And it seems the URL for core.js is right there in comment 9 and even attached... Oops. Please disregard comment 48.

I looked at core.js and didn't find any uses of innerHTML with script. (There were innerHTML uses with <style>, which is mildly worrying, mostly because I'm not aware of problems with <style> but problems are not unimaginable.)

It appears (based on off-Bugzilla info) that the exception is thrown after loading a binding (Backbase implements its own XBL-like language) that attaches to mutation events, so one line of investigation might be that whatever the portal does with innerHTML ends up firing different mutation events with the old and new HTML parser.

The bb object that is null per comment 9 is the object that hosts the Backbase engine implementation.

I tried Backbase's online demo of their product, and the demo seemed to work on Firefox trunk. So at least there doesn't appear to be an incompatibility with the hot code in the latest version of the Backbase engine.

CCing @backbase.com Bugzilla users in case they can tell us if Backbase is aware of an incompatibility between an old version of Backbase Portal and Firefox 4 and later and if this is just a case of EMC needing to update their Backbase libs to the latest version.

    
    

    
  
For all those unable to access the My Support section, the Search section uses the same technique which fails equally.

Login -> enter some search term -> click Search -> wait for result endlessly

    
    

    
  
Errors I get in the error console while trying to search something:

Error: bb is null
Source File: https://powerlink.emc.com/nsepn/webapps/btg548664833igtcuup4826/staticKmSearchResources/KM-3_20-20100423-112230-528/Backbase/engine/core.js
Line: 1

Error: uncaught exception: Error: Backbase Exception #12

Error: [Exception... "'JavaScript component does not have a method named: "observe"' when calling method: [nsIObserver::observe]"  nsresult: "0x80570030 (NS_ERROR_XPC_JSOBJECT_HAS_NO_FUNCTION_NAMED)"  location: "<unknown>"  data: no]

Probably the last being the cause.

    
    

    
  
(In reply to Jonas Nagel from comment #51)
> Error: [Exception... "'JavaScript component does not have a method named:
> "observe"' when calling method: [nsIObserver::observe]"  nsresult:
> "0x80570030 (NS_ERROR_XPC_JSOBJECT_HAS_NO_FUNCTION_NAMED)"  location:
> "<unknown>"  data: no]
> 
> Probably the last being the cause.

Does this show up every time? It looks like an error from the internal scripts of Firefox. It doesn't look like an error caused by site-supplied scripts.

    
    

    
  
(In reply to Henri Sivonen (:hsivonen) from comment #52)
>> Error: [Exception... "'JavaScript component ...
> Does this show up every time?

I get different output using 7.0a2, I can expand Uncaught Exception and get some multiline output but I am not sure how to interpret it nor how to actually copy it. The output is the same both for POWERLINK QUICK START and for search results. I do not get line about "JavaScript component".

If you explain how to capture console output with these errors, I am happy to provide them.

    
    

    
  
Same error here with FX 7.0 .... it keeps loading and loading and loading .... :(

    
    

    
  
(In reply to OlafHansenLebt from comment #54)
> Same error here with FX 7.0

Sure! This is a "Tech Evangelism" bug, not a bug in Gecko/Firefox.
EMC has to fix it. See comment 27.

    
    

    
  
(In reply to j.j. from comment #55)
> Sure! This is a "Tech Evangelism" bug, not a bug in Gecko/Firefox.
> EMC has to fix it. See comment 27.

I'm not so sure anymore. Seeing that every other browser EXCEPT FF/SM does it right, points in a different direction.

Also EMC says meanwhile, that it's not something they can/will fix, see comment 40.

    
    

    
  
> Also EMC says meanwhile, that it's not something they can/will fix, see comment 40.

Well, as long as they aren't interested to cooperate here it's unlikely that "Product: Tech Evangelism" will change. We need a testcase.

    
    

    
  
Comment 40 is not the least bit authoritative, considering it's hearsay that ostensibly came from a support lackey at EMC who likely has absolutely no control over the broken code.

We really do need a testcase, or someone who is affected willing to step up and do some further investigation.

    
    

    
  
I have a good relationship with EMC and I have access into the powerlink portal so whatever you guys need me to do I can do and I might be able to get in touch with someone who works with the actual site.

    
    

    
  
Well I don't deny that you do need an account on Powerlink, but I mentioned in comment 25 and comment 50, that anyone should be able to replicate the issue w/o problem and thus be able to develop a testcase - I'm not a devel, but I'm trying to help how I can.

    
    

    
  
(In reply to Jonas Nagel from comment #60)
> but I'm trying to help how I can.

Can you start by answering Henri's question from comment 52, then?

    
    

    
  
(In reply to Chris Lawson from comment #61)
> Can you start by answering Henri's question from comment 52, then?

Sure, I only assumed, that by now, as I taught how to catch the fish, anyone should be able to check it out.

Here you go:

The only error I get now reliably with SM 2.4 Beta is

Error: uncaught exception: Error: Backbase Exception #12

And that one shows up every time, as far I can tell, anything else mentioned before is unrelated, so Henri was right.

    
    

    
  
(In reply to Jonas Nagel from comment #56)
> (In reply to j.j. from comment #55)
> > Sure! This is a "Tech Evangelism" bug, not a bug in Gecko/Firefox.
> > EMC has to fix it. See comment 27.
> 
> I'm not so sure anymore. Seeing that every other browser EXCEPT FF/SM does
> it right, points in a different direction.

That doesn't prove anything. Other parts of the portal have browser sniffing. It's quite possible that the part that fails has browser sniffing going on, too.

I still don't have access to the part of the portal that fails, so I don't know for sure.

> Also EMC says meanwhile, that it's not something they can/will fix, see
> comment 40.

Is the person at EMC who said that a front-line support person who doesn't really know about the code or someone who actually knows the code? The failure appears to be in code from Backbase. Can EMC check if they are running the latest version of Backbase's product? If EMC is already running the latest version of Backbase's product, can EMC communicate with Backbase to figure this out?

Kev, do we have contacts at EMC who could get someone at EMC who actually knows about the Backbase integration to take a look?

    
    

    
  
(In reply to Henri Sivonen (:hsivonen) from comment #63)
> I still don't have access to the part of the portal that fails, so I don't
> know for sure.

If you registered on Powerlink (anyone should be able to do that), you should be able to search. When you're able to search, you'll see the Backbase failure, as pointed out in comment 50. With devel tools (and their understanding), someone might be able to see more.

If I saw that correctly, Backbase crew was already Cc'd here, but no reply so far.

    
    

    
  
(In reply to Jonas Nagel from comment #64)
> (In reply to Henri Sivonen (:hsivonen) from comment #63)
> > I still don't have access to the part of the portal that fails, so I don't
> > know for sure.
> 
> If you registered on Powerlink (anyone should be able to do that), 

I have a free account.

> you should be able to search.

I am unable to locate a search function using a free account. Can you give me step-by-step instructions for locating the search function, please?

    
    

    
  
(In reply to Jonas Nagel from comment #66)
> Created attachment 563448 [details]
> Search function to reproduce the issue

Not available for my free account.

    
    

    
  
(In reply to Henri Sivonen (:hsivonen) from comment #67)
> Not available for my free account.

Sorry to hear that. I didn't expect this to be unavailable to free users. Maybe ask Powerlink support to enable this under reference to this ticket, using the "Feedback" link top right (or is that one unavailable too?).

    
    

    
  
(In reply to Jonas Nagel from comment #68)
> Maybe ask Powerlink support to enable this under reference to this ticket,
> using the "Feedback" link top right (or is that one unavailable too?).

I sent a request. Let's see what happens.

    
    

    
  
I am currently working through my support channels at EMC to have someone look at this.  I gave them this bug number and I'm hoping they'll find someone in support to work with us on this.  The guys I spoke with said they weren't aware of this and would see if they could find someone who was.  They also asked me to put in a ticket regarding this so I am going to do that today and reference this thread.

    
    

    
  
EMC came back and told me they were able to get in touch with someone that's involved in the powerlink interface and they said this:

Firefox has changed the way the browser processed HTML, impacting certain parts of Powerlink used AJAX.  A workaround to the problem was provided by the IT Support Team, but the reach was limited because to implement, end-users needed to alter their browser settings.

The permanent fix will be deployed on October 8th, as part of our next release.  

--------------
So I guess we wait until Oct 9th to see if there is any progress.

    
    

    
  
> A workaround to the problem was provided by the IT Support Team, but the reach 
> was limited because to implement, end-users needed to alter their browser settings.

Let me guess: Comment 12 is the workaround provided by the IT Support Team.

But kudos to you for getting beyond the mere acknowledgment of the issue.

    
    

    
  
(In reply to Jonas Nagel from comment #72)
> > A workaround to the problem was provided by the IT Support Team, but the reach 
> > was limited because to implement, end-users needed to alter their browser settings.
> 
> Let me guess: Comment 12 is the workaround provided by the IT Support Team.

By which I assume you meant comment 13, but yeah, that was pretty much exactly what I was going to guess, too.

Paul, is that the case?

    
    

    
  
Chris: Not sure, never tried the workaround except to use IEtab.  

I did get a message from my contact at EMC and he said that they did some work over the weekend and to try it out.  I just tried it using firefox 7 and it seems to be working now.  Can anyone else verify this?

    
    

    
  
For testing please make sure you test with default setting!

Disable the sloppy "workaround" from comment 12:
- Go to about:config
- Enter   html5.parser.enable   in the filter box
- Changing it's value to true (default value)

    
    

    
  
Confirming it's working with SM 2.5 B2 too (not that the version mattered, as far we can tell now).

Not sure how this is handled usually, but I think we may reject or otherwise close this issue now. Thanks for all the collaboration on this, in order to put pressure on EMC.

    
    

    
  
Hooray. Thanks everyone.

Marking FIXED per comment 74 and comment 76.
Status: NEW → RESOLVED
Closed: 13 years ago → 13 years ago
Resolution: --- → FIXED
Product: Tech Evangelism → Tech Evangelism Graveyard

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






  

    
  







  

    

      
Attachment

      

      
      
      
      
    

    

      

        

          

            
General

            

              Creator: 



            

            
Created: 

            
Updated: 

            
Size: