Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
Is there something special about Safari for Windows and AJAX?
In other words: Are there some common pitfalls I should keep in mind?
Safari is really standards compliant. Unless you're using some really esoteric browser features, in general if something works in Firefox, I've found it works without modification in Windows Safari.
Apple has a developer center for web developers, but I didn't find anything too useful there.
In your event handlers, instead of return false, use event.preventDefault() or event.stopPropagation(). The event methods are the standard/compatible way, but lots of old tutorials still recommend return.
One word of warning: Safari on Windows does not support XSLT.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
I´d like to know. If I want to make a responsive website, should I use the "onmousedown" event? Would it be triggered on all devices?
I have tested the simulation of Firefox, on mobile I get the "onmousedown" event.
Is there such an event? That would be triggered on mouse down and/or on touch , in desktop and mobile devices?
Thanks.
Guarantee for all devices is nearly impossible due to the versions, nonstandard browsers, embedded browsers etc. You should first think about what your target platforms and what are the minimum browser versions. Then, you should follow the web standards and use common functions. Yes "onmousedown" is a standard event supported by majority of modern browsers, however it has also exceptions such as
The addEventListener() method is not supported in Internet Explorer 8 and earlier versions.
stated in the onmousedown documentation.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I'm sorry if this has been asked before.
Some ES6/7 standards are implemented in Firefox beta versions alone and not in Chrome, and vice versa. Can anyone please list which browsers support what? Is there any single browser which implemented most of those standards.
For e.g.: I'm not able to use Object.observe in Firefox. It is available in Chrome beta v36.
Please see: Do not mark duplicate for object.observe. I'm not interested in Object.observe There are other standards as well. Please specify others compatibility too.
See this table. It has a few mistakes in it, and glosses over the details (in particular, whether the implementation of a feature actually is complete and standard-conformant), but for most part it seems close enough.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
What is the difference between cross-browser javascript and multi-browser javascript? Do cross-browser and multi-browser mean the same thing?
Wikipedia link at http://en.wikipedia.org/wiki/Cross-browser mentions "multi-browser" to some extent but it seems to be unverified information. At some places people have used it to mean the same thing. So, I am bit confused.
Thank you in advance for your help.
Capturing my comment as an answer as suggested by FelixKling.
Cross-browser means something that works across all browsers whereas multi-browser means something that works on, well, multiple browsers.
You'll often see people cursing IE for lack of some or the other feature on articles which use latest CSS3 styles to achieve something wonderful. The solutions they present are multi-browser. When those solutions will start working on IE(in a year or so), they will be called cross-browser.
Is there a yardstick to define these terms? - No. They are notions and not standards and will remain so since anyone can whip up a browser with minimal support for all of standards.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I come from desktop application background and now I am working on web based application. So I am fairly new to client side script like Javascript.
I have a question that what set of standards we need to follow to make sure that our Java script code will work.
Any link for the same will be really helpfull.
That depends on what browsers you want to support. If you want to support pretty much everything, use the ECMAscript 3 standard. If you just want to support relatively recent browsers, you can use the ECMAscript 5 standard. Any features other than that and you can use this site to see about compatibility.
EDIT: For any other functionality that you think might not be very widespread, you can always check MDN as well.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
After a week of coding finally have my site working across all browsers and mobile devices. I made the mistake of not viewing in IE8 and IE 7 until now.
Can anyone share some steps in resolving IE7-8 compatibility issues when using jQuery and CSS?
What are some first steps to try?
If a site isn't too complex does it make sense to do server side detection and serve up an IE only site?
There should be few if any issues in jQuery - thats one of the big benefits to using jQuery or a similar library in the first place. Chances are if there is a js issue then its something you wrote as opposed to something internal to jQuery.
In both cases the bets thing to do is simply know the majority of the big things that differ in support. the Quirksmode.org compatibility tables are good for this. If you know the differences in the first place you are going to be able to create solutions up front before you ever get to testing and avoid the issues. Beyond that test cross-browser early on in the process - not at the last minute.
Depends on what problems you are running into. There are a lot of resources, such as PositionIsEverything or HasLayout, on the web complaining about & explaining different IE bugs (peekaboo, double margin etc).
It is useful to use a tool such as IETester to see your page on actual IE versions.