4 ms·
Just write proper markup, and you won't have this problem. It's 2015, different browsers don't need "ports" anymore for things like this. Validator: http://val
by ryannevius 12y ago
Just write proper markup, and you won't have this problem. It's 2015, different browsers don't need "ports" anymore for things like this.
Validator: http://validator.w3.org/check?uri=https%3A%2F%2Fwantrepreneurlist.appspot.com%2F&charset=%28detect+automatically%29&doctype=HTML5&group=0&user-agent=W3C_Validator%2F1.3+http%3A%2F%2Fvalidator.w3.org%2Fservices http://validator.w3.org/check?uri=https%3A%2F%2Fwantrepreneu...
- humanarity 12y agoI won't support FF because I don't use it. If you want to I don't mind :)
- deepsun 12y agoMan, you don't understand :) I don't use FF either, but by intentionally abandoning HTML standard you make yourself vulnerable to issues in Chrome, Safari or whatever you use. New version comes out, and your site's broken. It's not hard at all to comply to HTML standard, and just stop worrying about compatibility. Then you wouldn't even say the words "don't support <somebrowser>", because it's their problem that their browser doesn't follow standard.
- humanarity 12y agoThanks for that. I don't know much about Browsers and W3C, and maybe your idea works.