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.
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 8 years ago.
Improve this question
So if i excel at javascript than learning what other libraries, languages, framework, business related things would help me improve as a developer and get hired.
I know just knowing js isn't enough and that developer must know some basic stuff like
jquery, css3, html5, etc.
But what else.
I rarely see a job in which it says you need to know javascript there are always a lot of something else.
Well this is not the perfect place to ask this question but to help you I would like to suggest you some options.
If you are aiming to become a full-time front-end developer then along with the Javascript you must have excellent knowledge of HTML5, CSS3 and JQuery.
Also you must start practicing at least two of the following JavaScript frameworks:
Angular JS,
Node JS,
Grunt,
Dojo,
MooTools.
It would be good to have knowledge of SASS & COMPASS as well.
A good knowledge of Photoshop or Illustrator is also required.
Rest you can research yourself and choose as per your choice.
Best of luck!!
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.
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
What are the similarities between jQuery and Prototype?
For example, they both have selectors, although Prototype's general selector uses $$. They both also have the .hide method. Is there a good list of the similarities?
I know you're asking for similarities but its easier to answer what the differences are (from a users point of view they aren't massively different)
Migration Tutorial
Migration Cheat Sheet - That list you were looking for.
What are the current differences between jQuery and Prototype?
Prototype is a mature framework that does a very good job shoring
up browser differences and providing very well-rounded functionality.
Unfortunately it is a bit heavy-handed with its changes to the default
Javascript environment, and it's not seeing rapid development and
doesn't have a significant plugin ecosystem.
jQuery is a newer framework that was able to leverage some of the
lessons of the early javascript frameworks like Prototype to create
something more modular, less obtrusive, and significantly more
powerful and concise. I still love Prototype, but jQuery's DOM
manipulation and plugin ecosystem is just too good to ignore anymore.
If I was starting a greenfield project I'd have to go with jQuery
because that seems to be where the innovation is happening (at least
between those two choices).
Have you checked out this blog post at Ajaxian?
http://ajaxian.com/archives/prototype-and-jquery-a-code-comparison