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.
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 7 years ago.
Improve this question
I'm not looking for opinions but technical arguments to form my opinion. I know some people can't understand the difference, but it's a matter related to other proffesional area.
I'm trying to actualize my knowledge about HTML5 AND I'd like to know if modernizr.js is still useful to solve some client cravings. I'm reading material about HTML5, but the newest that talks about modernizr.js was published 3 years ago. I didn't find info in modernizr site newer than April 2013, neither a useful clearly actualized article published this year.
I'll appreciate any help.
Actualization:
No, there are no info actualized about what I'm looking for. Just tools to test, one by one, the elements modernizr tests. I have tested some elements listed in modernizr site. Every one is, at this day, supported by the browsers, so modernizr is not necessary for them. I'll check each element in order to decide if modernizr still could help or is dead.
Special thanks to ferr.
It depends on your users. Modernizr is meant to help you determine if you can use functionality that may be missing from some browsers and found in more modern browsers. If your users could possibly be using browsers that do not have functionality that you plan to use, and Modernizr is capable of helping you fill in that gap, then Modernizr is still useful to you.
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 8 years ago.
Improve this question
As I am learning vanilla JavaScript right now, I don't always know what to ask when searching through JS documentation (mostly on Mozilla MDN). So, I use what I know in jQuery until I get there.
So, what performance or other drawbacks should I be aware of when using jQ to substitute for my lack of full JS understanding while I learn?
These days, clients run fast enough that you don't really need to worry about any performance differences between vanilla JavaScript and jQuery. Thus, it could be said that this is a sort of "premature optimization", so I give you the same answer I always give: Use what you know/what's easier to maintain until you can demonstrate a critical performance bottleneck via a profiler; only then should you figure out how to improve the performance, possibly including switching to vanilla JS.
You should learn to understand how to retrieve elements from the DOM and how javascript relates to HTML. Basically you are altering html-elements and attributes.
http://en.wikipedia.org/wiki/Document_Object_Model
http://www.w3schools.com/js/js_htmldom.asp
https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model
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
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.
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
One of the interviewers asked to impress him with the JavaScript and CSS skills. He provided a link to two websites and asked to write a JavaScript application (page or pages) that takes content from one or both of these websites and demonstrates my command of jQuery and CSS. It doesn’t have to be useful to end-users, but it should be interesting to programmers.
What interesting things should I write? What would impress you in the candidate?
P.S.
The sites have real-estate information.
So, what would be the best way to read information from a given URL and extract some of it using jQuery?
That interview question is so subjective. What impresses one person might be basic to another. Why not ask a more meaningful question that demonstrates whether or not the candidate actually knows the language.
With all that said and if you really want to work for this company, I would study up on the basics of both js and jquery and really learn how to optimize basic functions. If you had to impress me then you should try to optimize a block of code as best you can without making the code unreadable. There's nothing better than clean, fast and readable code.