640536 - Getting XUL errors on standard webapp (pentaho, leading os tool for bi)

Status: RESOLVED DUPLICATE of bug 605087

(Core :: XUL, defect)

Description

[Pedro Alves]

In 4.0 I'm getting errors accessing pentaho application (www.pentaho.com). I'm getting "Error generating XUL", which is related to bug 546857 .


I just found out that installing extension Remote XUL Manager http://is.gd/yxi11P the application starts working again.


But should this happen in a standard GWT app? This is not trying to do anything with the chrome, it's just xml that's returned and translated into html on the client side.


The bug is also reported in pentaho's jira: http://jira.pentaho.com/browse/BISERVER-5282


This is the most widely used BI opensource tool, so it will have some negative impact if it doesn't work. 


You can reproduce the error by accessing the mozilla metrics site (ldap access required) in https://metrics.mozilla.com/pentaho/Home


Works fine in <=3.6

Comment 1

[Axel Hecht]

I see it loading https://metrics.mozilla.com/pentaho/mantle/xul/main_toolbar.xul

Comment 2

[Pedro Alves]

Yes - but it's a normal file that should be interpreted as regular xml on the client. Unless I'm interpreting it all wrong, but if you access it with chome, ie, etc, you'll see the same file being loaded and still works

Comment 3

[Axel Hecht]

It's referencing chrome://global/skin/, though, so it clearly tries to be XUL on the web, and we disallow that in Fx4 on purpose.

Comment 4

[Daniel Einspanjer [:dre] [:deinspanjer]]

Understood. If it references chrome, it is probably a bug on Pentaho's side since this file is served to other browsers as well.  Pedro, can you point them at this bug to tie up the loose end?

Comment 5

[Nick Baker]

Pentaho has it's own XUL engine which runs on Swing / SWT or in the browser through GWT. This is the source of the problem. We XMLHttpRequest the xul files down from the server where they're interpreted by the GWT js.

If the issue is with the xml directive:
<?xml-stylesheet href="chrome://global/skin/" type="text/css"?>

We have these removed. Directives aren't preserved in the DOM, and they're there simply to aid when designing XUL documents.

Comment 6

[Benjamin Smedberg]

The problem is the elements in the XUL namespace. Due to the way our DOM engine works, we cannot allow remote content to even create notes in that namespace. I recommend using an alternate namespace.