My OperaYou need to be logged in to post in the forums. If you do not have an account, please sign up first.
setting cookies from sever via php
Hello:I am working on a server side script that tests for cookies and javascript using php
and javascript (when it is active).
On my copy of Opera running on Mac OSX 10.5x (v 9.27). I am testing with cookies on
and javascript off. The browser is sent a <noscript> block with a link to
click manually to continue to the site index (because javascript redirect will not work).
Opera on Mac will not follow the link as it is programmed and winds up back
at the page with the link (this time the link does not appear).
When I use history and step back and reload the page (with the manual link)
the redirect works correctly.
This does not happen with Opera running on Windows Vista (v 10.53).
The question is: Is there a known bug with this version of Opera on
Mac; if so, is there a known workaround?
Please don't advise me to upgrade because I am doing web development that
will account for as many browser versions and platforms as possible.
If anyone gets around to reading, if not responding to this post, I have implemented an interim
solution: When the user gets to the page and is using Opera running on Mac, the user is advised to
reload the page before clicking the 'continue' link.
There does seem to be a critical difference between the way Opera 9x (at least) on Mac handles
cookies and the way Firefox, Safari on Mac and various versions of Firefox, IE, and Opera handle
cookies on Windows. They are accessible as soon as my manual link page loads.
With all the yahoo about standards, they are only relevant if the browser vendors actually get together
on them. Instead you have Object and embed tags for Flash, innerHtml for insertion of content after the
page loads, and many other fixes and workarounds that are 'nonstandard'. The most rediculous is the
conditional comments used in IE, and that is supposed to be 'standards complient'.
To ignore serverside generation of dynamic content, or neglect it just adds agony to the development process.
I am developing a system that uses server script to decide what css and javascript to load, as well as to
prescale graphics and font sizes for the users screen size. That is the purpose of this exercise.
Thank you for time and attention
JK
solution: When the user gets to the page and is using Opera running on Mac, the user is advised to
reload the page before clicking the 'continue' link.
There does seem to be a critical difference between the way Opera 9x (at least) on Mac handles
cookies and the way Firefox, Safari on Mac and various versions of Firefox, IE, and Opera handle
cookies on Windows. They are accessible as soon as my manual link page loads.
With all the yahoo about standards, they are only relevant if the browser vendors actually get together
on them. Instead you have Object and embed tags for Flash, innerHtml for insertion of content after the
page loads, and many other fixes and workarounds that are 'nonstandard'. The most rediculous is the
conditional comments used in IE, and that is supposed to be 'standards complient'.
To ignore serverside generation of dynamic content, or neglect it just adds agony to the development process.
I am developing a system that uses server script to decide what css and javascript to load, as well as to
prescale graphics and font sizes for the users screen size. That is the purpose of this exercise.
Thank you for time and attention
JK