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 5 years ago.
Improve this question
I'm at a job developing a dashboard application on the web.
There are about 50+ people working here (I'm the only programmer). While some computers have a decent version of Chrome installed, most only have IE to work with.
The newest version of Internet Explorer they have is IE10. Most have IE9 installed; some even have IE8.
I've already ditched Flexbox for the styling, which doesn't work on IE10 and down, but other features that work on modern browsers don't work on those older browsers at all, like scripts and some other features.
My question is: How can I get all these browsers to display the pages in the same way?
First, define the "official" list of supported browsers and OS's. It appears that you are working in a Microsoft environment so variations of IE on Windows may be the norm and not so much of Safari on Macs.
While making this list, convey to the decision makers that a bigger list usually means more time and effort to get everything working the same way for all of the supported configurations. Sometimes it makes more sense to upgrade a user using IE6 to something newer rather than spending weeks on an IE6 specific issue. (Re: IE6, do what you can to keep it off the list, doing so will save you a lot of time and aggravation.)
Another ramification of this list is that you, the developer, will need to have access to every configuration on the list so that you can test each supported configuration. Again, bigger list means more time developing AND testing.
Note that this list will change over time. Consider doing an annual review to revise this list as your environment evolves.
Once you've done the above, then it is a matter of recording the browser/OS variances and deciding which has the highest priority to fix. Fixes can be as simple as a one line CSS change or complex so as to require re-writing several pages.
If and when you get stuck, post another question on SO for ideas on how to fix specific browser/OS variances with your web dashboard application. Good Luck
Related
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 4 years ago.
Improve this question
I saw that on jQuery website it says that jQuery is "cross-platform"
But isn't that obvious?
could a browser be not compatible with jQuery?
Given that every browser is essentialy an interpreter for JavaScript,
and Given that jQuery IS JavaScript code.
Is it possible for me to write a js library that will not be browser compatible?
please help me make sense about this issue
thank you
Of course.
More broadly, a particular browser may interpret some version of JavaScript which is not the same version jQuery is written against.
Is it possible for me to write a js library that will not be browser compatible?
Yes.
In fact one of the huge selling points of jQuery is that it normalizes older browser APIs so that you're actually able to write less code in jQuery, compatible with more browsers, than if you wrote plain javascript.
It's less so the case now with modern browsers
[edit] just as an example, older browsers didn't always implement 'addEventListener' in the same way, particularly Internet Explorer, so jQuery would have normalized that.
Netscape 2.0 probably ...
Else, currents browsers integrates the V8 javascript engine and are based (on some build) on chromium project (chrome, opera, vivaldi, etc), because that are best.
That is why is useless, on today, to prefix, again, in 2018, the css properties or lost time to try to support all old browsers < 2016.
Furthermore JQuery is relativly useless in full pack, because ... V8 who implements lots of evolution.
At this day, you can code in full vanilla JS without need jQuery and without difficulties.
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
Im embarking on a project to build a new website.
From what I can see a lot of people are just going straight for css3 and ajax nowadays and not bothering to support browsers that dont have JS installed. They are using a number of workarounds such as enabling css3 through javascript in older browsers
Is this the ideal way now?
my suggestion would be what is called "progressive enhancement":
Progressive Enhancement means that each layer (content, followed by
markup, styles, and then behavior) builds upon the next, ensuring that
the core content is accessible along the way for less capable browsers
and devices. It’s not about specifics like whether your website works
with JavaScript, CSS3 Animations, or icon fonts. It’s not even about
technology. At its core, Progressive Enhancement means thinking about
a web page from the content out.
http://cognition.happycog.com/article/progressive-enhancement-its-about-the-content
start simple, and add Unobtrusive JavaScript and Css3 in a manner that, if not supported, they don't block the user from being able to navigate and use the website.
This really depends on the case. If you need to support older browsers like IE<9 and you need to do some fancy stuff not supported you can use a set of libraries 'faking' this new features for you. If you do not have to support older browsers or don't need to do fancy stuff you do not have a problem really. Check out http://www.caniuse.com to quickly see what features is supported in what browser (versions).
The question of cross-browser development, JS and CSS3 support, fallback, workarounds and degradation is the question of time and money. In some cases supporting of the old or non-trivial browsers could take about a half of the time you spent on development. Time is money. If you not sure such browsers will share a lot of the amount of visitors (which are your potential customers), should this time to be spent?
At the moment even IE8 shares only 4.31%. And it supports JS.
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
I'm using HTML5, CSS3, and other new technologies.
I want to prevent my users from using old browsers in a standard way.
How to detect old browsers in javascript or PHP?
How to show alert users properly?
This website provides a easy to use script that helps your users in a nice way to upgrade their browsers:
http://www.browser-update.org/
Include our small javascript notification on your website
Visitors with out-dated browser will be informed by a little, undisturbing bar, that his browser is not up-to-date and it is
recommended to update.
By clicking the bar, he will get to an info page with arguments why to change/update and some browser choices.
If the visitor ignores the advice, it won't appear again for some time.
It won't prevent the users from using your website, it will just notify them that they have an outdated browser and try to encourage them to update, and it does so in a discreet way.
By default, the script will give this message for a recommended set of old browsers (that automatically gets updated over time when browsers become too old), but you can also manually choose for which browsers the message will appear.
You're also able to customize the looks of the message.
Rather than diminishing peoples browsing experience by blocking them, consider progressive enhancement instead. While it may take a little more work it will be worth it. And as already suggested take a look at modernizr
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 am working on many browser issues. I got a doubt if is it possible to develop an application compatible with all browsers, or the vast majority, it needs to be web application.
Any suggestions on frameworks and tools?
Yes it's possible for the vast majority. I recommend you check out out
bootstrap - predictable layout across browsers & screen sizes
jquery - avoid browser specific javascript
Few advices on Javascript: Use 3rd party libraries which are masking compatibility issues. Examples:
jQuery: masks browser-specific event details, and fixes many other stuff
JSON2: fix for missing JSON definitions in certain browsers
html5shim: fix for html5 support in certain browsers
raphael: fixes SVG/VML mess with uniform API (useful if you use IE8 and lesser)
Regarding CSS and HTML compatibilites: it really depends on if you want to support IE prior to version 9. IE9 have most issues fixes.
There are hundreds of tools to assist with this, but really the best thing to do is learn web standards: http://www.w3.org
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.