XML on Older Browsers

Hi,
I have a client-side XSL component of my client's home page
so had to convert the page to XSLT. The page contains a Spry Tabbed
component with XSL-formatted XML data.
So when a user enters the domain name, I want the XML page to
display first so I put that in the htaccess file as the default
index.
But since older browsers are not XML compliant, how can I
display a non-XML ( plain HTML page ) for them? I don't think I can
put any logic in the xml or stylesheet since the XML file will not
be recognized by the older browser.
Is my only choice a straight index page that does redirects
based on the detected browser? That sounds like an awful kludgey
solution.
Should I give up on this and try XSL fragments server side
even though that's a bit beyond my current skillz? Is it correct to
think I can call an XSL fragment within an HTML page?
Thanks all for any advice

Hey there,
Animate only supports Animated content in modern browsers. IE <8 doesn't have the capability to handle some of the newer HTML languages. We do have an option to display a static poster image for older browsers and you can add links to different images.
Check out the poster/downlevel options which is what users will see on browsers that don't support CSS3.
You can also use Chrome Frame as an option to display animated content on older versions of IE. You can find this in the publish settings.
Sarah

Similar Messages

Supporting XHTML and older browsers (IE6) in WLP 9.2

Hi
We're trying to have a Portal that renders XHTML-1.0-TRANSITIONAL content.
In order to support older browsers, we have content-override set to "text/html".
However, WLP renders the script tags that link directly to .js files with just one self-closing tag.
<script src="/front/framework/skins/shared/js/Utils2.0.js" type="text/javascript" />
This confuses browsers, as it should (for compatability reasons) close it with an end tag, with emtpy content.
<script src="/front/framework/skins/shared/js/Utils2.0.js" type="text/javascript"></script>
Is there any way to control this behaviour?
Skeleton.xml
<ns:skeleton xmlns:ns="http://www.bea.com/servers/portal/framework/laf/1.0.0">
<ns:render-format>
     <ns:preset>XHTML_1_0_TRANSITIONAL</ns:preset>
               <ns:content-type-overrides>
                    <ns:override content-type="text/html" classification="allbrowsers"/>
               </ns:content-type-overrides>
     </ns:render-format>
</ns:skeleton>
client-classifications.xml
<classification name="allbrowsers" description="For everything">
     <useragent-regex value=".*" priority="5" />
</classification>
beehive-netui-config.xml
<jsp-tag-config>
     <doctype>xhtml1-transitional</doctype>
</jsp-tag-config>
...

Hi George and thank you for providing an answer to my problem.
We have actually worked around this. It's the same JS we are including on all pages, so we are doing this in head.jsp instead.
However, we have found another XHTML compliance problem. This is hopefully the last one though. ;)
When using NETUI, it will include a javascript for looking up tags by id.
<script language="JavaScript" type="text/JavaScript">

</script>
The problem here is the language="JavaScript" part, since that is not valid XHTML.
I would have thought that NETUI should respect the <jsp-config><doc-type> set to XHTML, but maybe I'm overseeing something?

Why won't my Edge Animate play on older browsers (IE 7 for example)?

I've created an Edge animation (marquee) banner for a site I'm working on, but when I check it on older computers (for example XP running IE7), all I see is a large white rectangle where the marquee is supposed to be. Any ideas?

Hey there,
Animate only supports Animated content in modern browsers. IE <8 doesn't have the capability to handle some of the newer HTML languages. We do have an option to display a static poster image for older browsers and you can add links to different images.
Check out the poster/downlevel options which is what users will see on browsers that don't support CSS3.
You can also use Chrome Frame as an option to display animated content on older versions of IE. You can find this in the publish settings.
Sarah

PNG8 and 32 in older browsers

Im making a site that has a semi transparent image as a background image for a div with text.
Im looking at using a PNG8 or 32, but how and will these degradee in older browsers? If they become opaque thats fine, but if they dissapear then the text will be hard to read.
Thanks

In IE6 any transparent png will appear with a grey box. You can use this png fix to solve that problem
http://www.twinhelix.com/css/iepngfix/

How to disable the alert message that comes in older browsers while loading

Hi!
I'm testing the ADF Rich faces app on Firefox 2.0.01.
It's working fine, but still I get the Error "" You are using unsupported Gecko Browser,the Supported Gecko browsers are 2.0.02 and higher".
I don't want that message to be displayed to the user, though he may be using older browsers..
I Suppose the application developer can handle it according to the demands of the of the situation...
Can you suggest a way to disable that alert message which is very annoying to the user , every time a page is loaded ?
Thanking you in advance,
Samba

I filed your complaint as an ER. For tracking purposes the ER number is 6160631.
--RiC

Which older browsers don't work with iWeb '08?

I've created a new site in iWeb using a blog page as the default page. My wife couldn't see any of the blog entries using an older Mac and Safari 1.x. So that makes me wonder, what other older browsers are incompatible with iWeb?
Specifically since so many Windows users are still stuck with IE6, I wonder if these users could see my site at all? If not, I'm going to have to re-create the site using other software.
Would anyone who has access to IE6 for Windows be willing to check out http://www.gardensofstationpointe.com and let me know if you can see the blog entries listed?
Thanks.

Thanks for checking. I actually switched the site to RapidWeaver since I asked the question. I was afraid the original iWeb site wouldn't work with older browsers. I forgot to come back here and make note of it. Thanks.

Are there any of the older browsers we can be using right now?

I know from the past, we've used older versions in times , there were problems. I would like to know which ones to use that work good, and are safe.There's been so many browsers over the years, I'm not sure which ones to try. Thank You.
"application": {
"name": "Firefox",
"version": "24.0",
"userAgent": "Mozilla/5.0 (Windows NT 5.1; rv:24.0) Gecko/20100101 Firefox/24.0",
"supportURL": "https://support.mozilla.org/1/firefox/24.0/WINNT/en-US/"
"modifiedPreferences": {
"browser.cache.disk.capacity": 358400,
"browser.cache.disk.smart_size.first_run": false,
"browser.cache.disk.smart_size.use_old_max": false,
"browser.cache.disk.smart_size_cached_value": 358400,
"browser.places.smartBookmarksVersion": 4,
"browser.startup.homepage_override.mstone": "24.0",
"browser.startup.homepage_override.buildID": "20130910160258",
"dom.mozApps.used": true,
"extensions.lastAppVersion": "24.0",
"network.cookie.prefsMigrated": true,
"places.history.expiration.transient_current_max_pages": 20118,
"places.database.lastMaintenance": 1381199361,
"plugin.importedState": true,
"plugin.disable_full_page_plugin_for_types": "application/pdf",
"privacy.sanitize.migrateFx3Prefs": true,
"storage.vacuum.last.places.sqlite": 1380244034,
"storage.vacuum.last.index": 1
"graphics": {
"numTotalWindows": 4,
"numAcceleratedWindows": 0,
"windowLayerManagerType": "Basic",
"windowLayerManagerRemote": false,
"numAcceleratedWindowsMessage": [
"tryNewerDriver",
"9.6"
"adapterDescription": "RADEON 9200 PRO Family (Microsoft Corporation)",
"adapterVendorID": "0x1002",
"adapterDeviceID": "0x5960",
"adapterRAM": "Unknown",
"adapterDrivers": "ati2dvag",
"driverVersion": "6.14.10.6462",
"driverDate": "3-23-2004",
"adapterDescription2": "",
"adapterVendorID2": "",
"adapterDeviceID2": "",
"adapterRAM2": "",
"adapterDrivers2": "",
"driverVersion2": "",
"driverDate2": "",
"isGPU2Active": false,
"direct2DEnabled": false,
"directWriteEnabled": false,
"directWriteVersion": "0.0.0.0",
"direct2DEnabledMessage": [
"tryNewerDriver",
"10.6"
"webglRendererMessage": [
"tryNewerDriver",
"9.6"
"info": {
"AzureCanvasBackend": "skia",
"AzureFallbackCanvasBackend": "cairo",
"AzureContentBackend": "none"
"javaScript": {
"incrementalGCEnabled": true
"accessibility": {
"isActive": false,
"forceDisabled": 0
"libraryVersions": {
"NSPR": {
"minVersion": "4.10",
"version": "4.10"
"NSS": {
"minVersion": "3.15.1 Basic ECC",
"version": "3.15.1 Basic ECC"
"NSSUTIL": {
"minVersion": "3.15.1",
"version": "3.15.1"
"NSSSSL": {
"minVersion": "3.15.1 Basic ECC",
"version": "3.15.1 Basic ECC"
"NSSSMIME": {
"minVersion": "3.15.1 Basic ECC",
"version": "3.15.1 Basic ECC"
"userJS": {
"exists": false
"extensions": [
"name": "Troubleshooter",
"version": "1.1a",
"isActive": true,
"id": "[email protected]"
"name": "avast! WebRep",
"version": "7.0.1474",
"isActive": false,
"id": "[email protected]"
"name": "DnsBasic",
"version": "1.0",
"isActive": false,
"id": "{650EED71-89E2-453B-8DCF-2AA1B4AE6EF3}"
"name": "KnowtheBible",
"version": "5.24.1.48262",
"isActive": false,
"id": "4lffxtbr@BibleTriviaTime_4l.com"
"name": "Microsoft .NET Framework Assistant",
"version": "0.0.0",
"isActive": false,
"id": "{20a82645-c095-46ed-80e3-08825760534b}"
''merged old thread details with thread. -mjb''

As already posted, best is always to identify and solve problems instead of downgrading to older Firefox versions.
Only the Firefox 17 ESR and Firefox 24 ESR versions in the future can be considered as older Firefox versions as long as they are supported with security updates.
*http://www.mozilla.org/en-US/firefox/organizations/all.html
All older Firefox versions have security issues that make you vulnerable to malicious websites.
If websites only work with older Firefox versions and not with the current release then best is to use a portable Firefox version only for those websites and use the current release for all other websites to be protected as good as possible.<br />
The portable version comes with its own profile folder and doesn't interfere with the currently installed release version.
*http://portableapps.com/apps/internet/firefox_portable
*http://portableapps.com/apps/internet/firefox_portable-esr
*http://portableapps.com/support/firefox_portable#helper_apps

CSS3 support for older browsers

It's pretty clear now that CSS3 is a Rubicon for web browsers and that either the browser is capable of interpreting the rules or it is not. Having said that, is there a "patch" of some sort that can be painlessly added to the CSS to allow support for, say, IE8?

I'm with Mark. Build to the level of your main target audience -- not the fewer than 5% who insist on using outdated browsers.
I have experimented with PIE and other so called "workaround" scripts for IE with less than stellar results. Also , IE Filters have some nasty side effects -- like disabling clearType which makes text look really terrible. I view these "workarounds" as mainly counterproductive.
Going forward, I'm adding an IE8 End Of Life message inside a conditional comment in all my projects now. That way people know up front that their browser sucks. The ball is then in their court whether or not to do anything about it.
We still have an XP computer at home that hubby doesn't want to part with. So the only IE browsers he can use are 7 & 8. That said, his favorite browsers are the latest versions of FF and Chrome which he uses regularly on XP. Just because some people have an older operating system doesn't necessarily mean they have to use inferior browsers.
Unless it's adversely effecting your content or usability, I don't think you should do cartwheels to support the few remaining IE7 and IE8 users. It's better for everyone if we ween them off the bad browsers as soon we can.
Nancy O.

Compatibility with older browsers

I was surprised to see WLP8.1 being marketed as only supported on IE 5.5,
Mozilla 1.2 and NS 7.0. For larger corporations, and customer-facing B2C
websites, it does not make sense to shut out 5-10% of the users just because
they are on older platforms...
Having said that, does anyone know how to get WLP 8.1 to work with Netscape
4.x and IE 4.x? I assume we would need to create a new skin with all
compliant CSS and JS files - has anyone had any success with implementing
something similar? Id appreciate any pointers on how to get started in the
right direction.
Thanks!
Soumit

When I used borders before Swing I created one panel
for each type of border I wanted. Let the panels paint-
method draw lines along the panels borders.
Something like:
public class FrameBorder extends Panel
public void paint(Graphics g)
Dimension d = getSize();
Point p = getLocation();
g.draw3DRect(p.x,p.y,d.width-1,d.height-1,true);
g.draw3DRect(p.x+2,p.y+2,d.width-5,d.height-5,false);
Should not take to much testing to come up with some nice-
looking borders.
/J

IE11 no longer recognised stating the site doesn't support older browsers and to update.

How can IE11 not be recognised. I've seen this on other sites and would not have expected to see it at Adobe sites, especially the Creative Cloud site. Rendered the whole Cloud useless for Windows 8 users.

Hi John,
You may be having no problems on W7, but on Windows 8.1 (update one) no updated CC site will play with IE11, they detect it as being IE8. I'm using AGV internet security 2014 and their firewall as you asked, but can't see how this has anything to do with Adobe websites wrongly identifying the browser. All was working perfectly well until they changed things. I shouldn't be having to tweak things this end to accommodate Adobe they should ensure their site detect all mainstream browsers correctly as thousands of other sites do.
It's becoming clear to me that Windows whatever its version, is just seen as an irritant to Adobe and they would much prefer to just develop for Apple, its products and devices. Why they just can't be honest I don't really know. But then again maybe I do.
Taken me 20 mins just to login to the forums to respond too you trying both IE11 and Firefox, I just give up.
Regards,
Pat Doyle

IPhoto, older browsers, and settings

I have searched and haven't found an answer for this, so I'm posting. My apologies if it's been covered.
I used to use earlier versions of iPhoto to publish photos for my family. Now that I've gotten a new computer and am using the latest version of iPhoto, I'm confused. Sure the new snazzy effects are nice, but no one in my family (they use older iMacs and average Windows machines) can see my photos.
I've looked and looked, but can't find a setting to simplify it when the page is created. I like ajax as much as the next guy, but sometimes can't things be simple if necessary? I really, really want to keep this simple and just throw my photos up so I can focus on other things like not doing this myself.
Any suggestions? Kindest thanks for any help.

Christopher:
Welcome to the Apple Discussions. The problem is with Safari. Suggest they try a newer version of Safari if it will run on their system or switch to Firefox 2 (the V3 version doesn't work).
Or have them try dowloading a newer version of WebKit from Nightly Builds and launch it instead of Safari. It will open Safari when it launches. WebKit is the underpinning of the Safari browser and some others. There are a number of different versions and they can try several until they get one that works.
I'm using Safari 2 with one of the latest WebKits and it works great.
TIP: For insurance against the iPhoto database corruption that many users have experienced I recommend making a backup copy of the Library6.iPhoto (iPhoto.Library for iPhoto 5 and earlier) database file and keep it current. If problems crop up where iPhoto suddenly can't see any photos or thinks there are no photos in the library, replacing the working Library6.iPhoto file with the backup will often get the library back. By keeping it current I mean backup after each import and/or any serious editing or work on books, slideshows, calendars, cards, etc. That insures that if a problem pops up and you do need to replace the database file, you'll retain all those efforts. It doesn't take long to make the backup and it's good insurance.
I've created an Automator workflow application (requires Tiger or later), iPhoto dB File Backup, that will copy the selected Library6.iPhoto file from your iPhoto Library folder to the Pictures folder, replacing any previous version of it. It's compatible with iPhoto 6 and 7 libraries and Tiger and Leopard. iPhoto does not have to be closed to run the application, just idle. You can download it at Toad's Cellar. Be sure to read the Read Me pdf file.≤br>
Note: There now an Automator backup application for iPhoto 5 that will work with Tiger or Leopard.

Why is my page collapsing in older browsers?

I tested my page in Firefox 3.5.2 and IE 8 (actually 8.0.6001.18702) and it works fine. But when I tested it on another machine and used IE 7. the footer and main (body) area collapsed over the header. Can anyone check it out and let me know how I can make changes for all browser types?
Here is the link: http://shepardsuperteam.com/chris/index.html

Run your code through the on-line validation tools below and fix any reported errors. You have a malformed division ID near the end of your page. No spaces allowed in Div IDs.
HTML Validator - http://validator.w3.org
CSS Validator - http://jigsaw.w3.org/css-validator/
Nancy O.
Alt-Web Design & Publishing
Web | Graphics | Print | Media Specialists
www.alt-web.com/
www.twitter.com/altweb
www.alt-web.blogspot.com

Legacy project vs new browsers

Hi all, I have one client project for whom we still use TCS1, for updates about twice a year. This is the only client we use it for, so we have never upgraded. We do have a copy of RH10 standalone, but otherwise we have been increasingly using Flare (I am the lone hold-out, I like RH).
So the client has just observed that the webhelp cannot be viewed in Chrome, and I confirmed that that was a known issue. I suggested that HTML5 might be a better output for newer browsers/versions, so the options would be to upgrade to the current TCS ($1200 the boss is not anxious to absorb for one client), or convert the project to Flare (which might be a better solution to use Lingo for translation). The client is reluctant to switch to HTML5 because some clients still use older browsers, e.g. IE8, that don't fully support HTML5.
I also just discovered that the current help files don't work in IE10 (topic pane is blank). I know RH10 and 11 have a fix for this. So I had the brainwave to upgrade the RH project, after conversion into RH8 via TCS, to RH10, so that the webhelp *should* work in all browsers/versions.
Unfortunately, RH10 would not comply. First I got the message "Error in reading RHFrameStyleMappings.apj file", followed by "Open project was cancelled or the application was unable to load database for <cpd filename>". I deleted the cpd file, and then the apj file, but got the same messages.
Do you see any way to get Webhelp that works in older and newer browsers, using the tools I currently have?
I appreciate any input,
Laurie

Thanks, Willam, I'll try that. The immediate concern has been alleviated, as the developer has confirmed that they are able to open the existing help files, as created with TCS1, in IE10 without any problem. They didn't work for me on the test site I had access to, but confirmed they worked on a different site. He told me he had to make the following change to the webserver:
"What happens is helpfiles uses xml files that were blocked by the application’s web.config file via this line…
<add name="xml" verb="*" path="*.xml" type="System.Web.HttpForbiddenHandler" />
I had to change it to…
<add name="xml" verb="*" path="model.xml" type="System.Web.HttpForbiddenHandler" />"
So we are ok for now, but I think a tool change is inevitable. Based on internal discussions, the consensus is that if the client is determined to continue requiring a PDF, we should upgrade to TCS, because it was felt that Word would choke on an almost 500-page output en route to generating the PDF. However, if they are willing to drop the PDF, and are serious about getting into translation, Flare/Lingo might be the better route.

XML Anywhere TO Write Once , Run Everywhere

I proposed this 4 years ago to cho haha reply.
All codebase languages , legacy codebase , legacy code , etc . . . standardized into am XML file.
MVC no. XVC yes. Xml View Controller yes.
Xml Namespace yes. Xml Redirection_One Namespace yes.
Xml Redirection_Two Namespace yes.
No one says the word XHTML let alone XDHTML. Or SGML.
At Intel Forum-- [http://communities.intel.com/people/ajaytemp?view=profile] -------
The World Wide Web Consortium (W3C) is the main international standards organization for the World Wide Web (abbreviated WWW or W3).
Founded and headed by Tim Berners-Lee,[2] the consortium is made up of member organizations which maintain full-time staff for the purpose of working together in the development of standards for the World Wide Web. As of 10 July 2011, the World Wide Web Consortium (W3C) has 317 members.[1]
W3C also engages in education and outreach, develops software and serves as an open forum for discussion about the Web.
Is HTML3,4,5 in conformance to XML or XHTML ? Or X-HTML ? Why is ther HTML and then XHTML. I didn't see SGML consortium.
This fissure or crack which seems to have caused a bumpy road for Web Browser producers is really annoying.
It won't cause problems is really dumb.
XML has been around for a decade or so . . .
So if I write XHTML code. Will older browsers show it ?
I felt like there is HTML and then there is XHTML.
HTML requires a DTD tag at top which is really weird if you ask a layman what that is. Some standard from really old days.
THen there is HTML transition standard, a 2nd , a 3rd... If it's a standard and everyone could write HTML code and be a public publisher or FREE speech.
Then certain keywords are deprecated in one version, another version it's good to show. Makes no sense what is going on with browsers and their best attempts to get close to a W3C standard.
Shame.
They have strict, frameset, and then transitional versions of HTML, DHTML, or XHTML, XDHTML. What's the need for four or five more Standards. Not a standard even a Protocol now.
It would of been easier to write Mandarin (chinese) code in ISO C or ANSI C then put up a simple egnlish home page i write in word pad or note pad.
They Javascript Event Handling Methods are deprecated. A new one is added.
It's really all unncessary. And this is making students life difficult is understatement.
UGGGGGGGGLY.
See Berkshire Hathaway home site for QUALITY HOME PAGE. Always see GOOGLE.COM home site. Quality matters.

Large corps can't cooperative with college grads with COOP. Fine. It doesn't matter with .xml Lingua Franca .
Older systems have compatibility now with the 3 letter extension !
corperative dot_xml

POODLE Vulnerability and AMS configuration in Adapator.xml

Hi,
I am looking for some recommendation and guidance on how to ban AMS from using SSlV3 in with RTMPS clients. I know about that there's a configuration in Adaptor.xml called
"SSLCipherSuite" which should be able to somehow prevent a specific protocol, but the Adobe documentation recommends contacting with Adobe before changing that configuration.
So I was wondering if Adobe has any official recommendation to prevent RTMPS client from using SSLV3. Could someone please point me to the right direction?
Thanks
-Irtiza

When will it be released?
I can not comment on that...
How will it support older browsers?
Well most likely it will disable SSLv3 support from within the application. So you will not need to change anything in AMS ocnfiguration.
All browsers which work on TLS 1.0 and higher will continue to work as they were working till now.
Note that even in current release, if your browsers support TLS then TLS would be preferred mode of connection and you will not be exposed to SSLv3 attack.
Even today, POODLE vulnerability exists only if you are working on those browsers which do not support TLS.
That said, you must upgrade your openssl to 1.0.1j, because prior to that a hacker could exploit a hack in openssl so that even if your endpoints supports TLS, it can hack and make the connection protocol get downgraded to SSLv3...openssl to 1.0.1j fixes this downgrade protocol attack..
The steps to compile openssl for AMS are available in public domain..please google and compile openssl for yourself and drop that openssl in your AMS installation.
Openssl consists of two files libeay32.dll and ssleay32.dll on windows AND libssl.so.1.0.0 and libcrypto.so.1.0.0 on Linux...

XML on Older Browsers

Similar Messages

Maybe you are looking for