3 ms·

First of all, thanks for your answer. > And the answer is: "Microsoft Internet Explorer, Firefox, Chrome, Opera, and Safari". Well, my main issue is that test

by phn 14y ago

First of all, thanks for your answer. > And the answer is: "Microsoft Internet Explorer, Firefox, Chrome, Opera, and Safari". Well, my main issue is that testing in so many browsers, and making adjustments for each one seems to go a bit against the goal of standards. > And do all you can to use standard methods -- avoid techniques that only work on one or two browsers, or that break widely accepted browser standards. Is there any way one can test/learn this? I would love to have a solid "standards compliant" base knowledge to at least be aware of when I'm doing something outside of standards. > Without seeing what you code, this is impossible to say. Of course :) I was talking in a general way. Once again, thanks.

lutusp 14y ago
> Well, my main issue is that testing in so many browsers, and making adjustments for each one seems to go a bit against the goal of standards. But your goal isn't standards, your goal is to make pages that all your visitors will see the same way. That means you need to adapt to the present realities of Web development. >> And do all you can to use standard methods ... > Is there any way one can test/learn this? Sure -- read the specifications. Examples: http://xhtml.com/en/xhtml/reference/ http://xhtml.com/en/xhtml/reference/ http://www.w3.org/html/wg/drafts/html/master/ http://www.w3.org/html/wg/drafts/html/master/ My point is that this is not easy to do.
- lutusp 14y ago
  I offer this addendum to my prior comment: http://www.paulzaich.com/2013/02/21/blog/ruby-rails/https-gotcha-in-ie8/ http://www.paulzaich.com/2013/02/21/blog/ruby-rails/https-go... Title: "Always test your app in IE8" Quote: "A simple 1 character change from ‘http’ to ‘https’ on the shim was all that was needed to fix the problem, but it had been lurking there for several weeks unseen because we only were testing on 'modern browsers'."
Piskvorrr 14y ago
> Well, my main issue is that testing in so many browsers, and making adjustments for each one seems to go a bit against the goal of standards. The state of the Web is currently closer to a single standard than it's ever been in its history. Nowadays, it's fairly easy to make the adjustments - or even use libraries which abstract the most discrepancies. It could be better, of course - but one has to work with the world as it is, not as it should be :)
27182818284 14y ago
This is easier now than ever. Lately I've had a lot of luck writing something once and having it work with IE10, Chrome, and Firefox immediately. That leaves only fixes for IE8 and IE9. By designing things to be responsive from the get go, mobile is 98% supported off the bat too with only small fixes needed thanks to Webkit's majority. I would suggest starting with a base such as Bootstrap (or another framework of your liking) and getting a Browserstack account. Testing becomes much easier with Browserstack and they were offering three months free with a coupon, so give them a try.

by phn 14y ago

lutusp 14y ago

> Well, my main issue is that testing in so many browsers, and making adjustments for each one seems to go a bit against the goal of standards. But your goal isn't standards, your goal is to make pages that all your visitors will see the same way. That means you need to adapt to the present realities of Web development. >> And do all you can to use standard methods ... > Is there any way one can test/learn this? Sure -- read the specifications. Examples: http://xhtml.com/en/xhtml/reference/ http://xhtml.com/en/xhtml/reference/ http://www.w3.org/html/wg/drafts/html/master/ http://www.w3.org/html/wg/drafts/html/master/ My point is that this is not easy to do.

lutusp 14y ago
I offer this addendum to my prior comment: http://www.paulzaich.com/2013/02/21/blog/ruby-rails/https-gotcha-in-ie8/ http://www.paulzaich.com/2013/02/21/blog/ruby-rails/https-go... Title: "Always test your app in IE8" Quote: "A simple 1 character change from ‘http’ to ‘https’ on the shim was all that was needed to fix the problem, but it had been lurking there for several weeks unseen because we only were testing on 'modern browsers'."

Piskvorrr 14y ago

> Well, my main issue is that testing in so many browsers, and making adjustments for each one seems to go a bit against the goal of standards. The state of the Web is currently closer to a single standard than it's ever been in its history. Nowadays, it's fairly easy to make the adjustments - or even use libraries which abstract the most discrepancies. It could be better, of course - but one has to work with the world as it is, not as it should be :)

27182818284 14y ago

This is easier now than ever. Lately I've had a lot of luck writing something once and having it work with IE10, Chrome, and Firefox immediately. That leaves only fixes for IE8 and IE9. By designing things to be responsive from the get go, mobile is 98% supported off the bat too with only small fixes needed thanks to Webkit's majority. I would suggest starting with a base such as Bootstrap (or another framework of your liking) and getting a Browserstack account. Testing becomes much easier with Browserstack and they were offering three months free with a coupon, so give them a try.