• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Cross Browser Compatibility Issues

 
Ranch Hand
Posts: 421
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello I am working with some code which was created a few years ago.

It is not cross browser compliant. The only browser it works on is IE.

I was wondering if you could direct me to some resources where I could find some information about cross-browser compatibility for this site.

I noticed that these pages have this at the top of the xsl pages:

<xsl:output method="html"/>

If I remove that, then I get a description for products, however, it is in html instead of in plain text.

Thanks,

 
Sheriff
Posts: 67746
173
Mac Mac OS X IntelliJ IDE jQuery TypeScript Java iOS
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I assume that that's the line that instructs XSL to convert the document. Without it, the document is unlikely to be converted. Is that what's going on? I'm not sure I see what that has to do with browser compatibility.
 
Michele Smith
Ranch Hand
Posts: 421
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
The following is an example. There is no syntax referring to XSLProcessor in the entire project. Neither is there any reference to processXSL.

However, the xsl might say something like this:



This works on IE but not on Chrome or Firefox. (the "Name" value of the xsl).

Thanks,
 
Bear Bibeault
Sheriff
Posts: 67746
173
Mac Mac OS X IntelliJ IDE jQuery TypeScript Java iOS
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
XSL is a subject better discussed in the XML forum, so I have moved this topic there.

If what you are really having problems with is the HTML or JavaScript that's being generated after the XSL processing, then post back with the rendered source that you are having problems with.
 
Marshal
Posts: 28193
95
Eclipse IDE Firefox Browser MySQL Database
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Bear Bibeault wrote:I assume that that's the line that instructs XSL to convert the document. Without it, the document is unlikely to be converted.



It's the line that instructs XSLT to convert the document to HTML. Without it, the document will be converted to XML unless the document is "recognizably HTML", i.e. its root node is an <html> element. (That's a rough approximation of what the spec says.)
 
Bear Bibeault
Sheriff
Posts: 67746
173
Mac Mac OS X IntelliJ IDE jQuery TypeScript Java iOS
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I guess I'm still kind of confused about what the real issue is. Is it that the XSL is not working as expected, or is it that the rendered HTML and script is not working correctly after the conversion?

If the former, I seem to recall that XSL is not automatically triggered in any browser but IE? But I could be completely wet as I left XSL back in 1998 (where I think it still belongs ).
 
Paul Clapham
Marshal
Posts: 28193
95
Eclipse IDE Firefox Browser MySQL Database
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Yeah, XSLT in the browser is definitely one of those "It seemed like a good idea at the time" architectures, and you don't hear much about it any more, but I do think that browsers other than IE were made to implement it quite a few years ago.

Of course what I'm thinking of is the architecture where you send an XML document to the browser, and that XML document has a processing-instruction at the beginning linking to an XSLT document which is supposed to be used to transform the XML document to HTML for the browser to display. But from what I've seen in this thread, I have no idea whether that's the concept being asked about.
 
Michele Smith
Ranch Hand
Posts: 421
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Paul:

Is this what you mean?

http://docs.oracle.com/cd/B10501_01/appdev.920/a96621/adx05xsj.htm#1012620

Thanks,
 
Paul Clapham
Marshal
Posts: 28193
95
Eclipse IDE Firefox Browser MySQL Database
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
No, that wasn't at all what I meant. And it doesn't mention browsers at all, so surely it wasn't what you meant either?
 
Paul Clapham
Marshal
Posts: 28193
95
Eclipse IDE Firefox Browser MySQL Database
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
This is what I meant: http://www.w3schools.com/xsl/xsl_transformation.asp... scroll down to the section headed "Link the XSL Style Sheet to the XML Document".

But what I meant is not very relevant. This is your thread, so we need to know what you meant.
 
Michele Smith
Ranch Hand
Posts: 421
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
The following are empty when I preview in Firefox or Chrome:

Local Name
Local Description
Wholesale
THUMBNAIL IMAGE

 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic