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.
Related
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 5 years ago.
Improve this question
I am trying to show a Bokeh plot in Firefox. There are quite many sub-graphs (approximately 200), each showing 1-4 objects.
I am receiving in Firefox:
"A webpage is slowing down your browser."
Some notes:
After rebooting, it works fine for a couple of times.
I am behind a corporate proxy. I ask myself if it may be the cause. Some JavaScript and CSS is being loaded from cnb.pydata.com.
It sounds like your Firefox version is having issues with said webpage. Although I'd say that the design of such site trying to show 200 JS driven plots seems questionable.
As far as I know, there is little that you can do besides updating Firefox, they have been busy lately improving many elements of performance, or trying another browser with better JS performance like Chrome.
If you're in a corporate network it might be many not possible for you to upgrade or install, then you have to go to you IT department looking for help.
Now, since you're generating the HTML with the graphs, perhaps would it be a better idea for you to make a "dashboard" where you show a few and then use dropdown menus or sliders to control which plots are shown at any given time. I've seen solutions using using bokeh itself to do so, or if you want eventually somethign fancier you can also use flask.
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
There are many ways to use JavaScript. When I use JavaScript with an anchor, I write code like this and I think this way is right.
Method One
But my co-worker uses JS like this.
Method Two
Is there a coding standard or are both methods correct?
DISCLAIMER: Inline JavaScript is, generally speaking, a bad idea, and 99% of the time you're much better off separating concerns, and using a library, such as jQuery, or whatever similar toolset that your framework of choice recommends.
Nonetheless, to answer your question, if you must use inline JavaScript, I recommend that you omit the "JavaScript:" keyword. It specifies a "pseudo-protocol," and is not necessary for modern browsers to interpret the code. It is a relic from the last decade, and there is a bug with some versions of IE:
"There is one (somewhat obscure) bug with the javascript protocol - in
Internet Explorer*, it will think you are leaving the page when you
click the link. If you are using window.onbeforeunload, then your
navigate-away message will appear at this time. For this reason alone,
we've stopped using the javascript protocol completely so we don't
have this bug show up because we forgot to check for it when we add a
navigate-away message to some page."
When do I need to specify the JavaScript protocol?
https://bytes.com/topic/javascript/answers/504856-javascript-pseudo-protocol-event-handlers
Both the ways are ok but in first way you should use a external JS file. Otherwise it is ok.
For small tasks and events second ways is good.
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
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