If you can read this, either the style sheet didn't load or you have an older browser that doesn't support style sheets. Try clearing your browser cache and refreshing the page.

(Ars Technica)   After spending years convincing Web devs that they should design sites primarily for IE since it was the most popular browser, Microsoft is now asking Web devs to design sites for all mobile browsers, not just the most popular one   ( arstechnica.com) divider line
    More: Obvious, mobile browser, Internet Explorer 10, Internet Explorer, Microsoft, WebKit, Redmond, World Wide Web Consortium, browser  
•       •       •

1762 clicks; posted to Geek » on 17 Nov 2012 at 6:17 PM (5 years ago)   |   Favorite    |   share:  Share on Twitter share via Email Share on Facebook   more»

Voting Results (Smartest)
View Voting Results: Smartest and Funniest

2012-11-17 05:44:38 PM  
2 votes:
It's what you say when you are no longer popular.

/and fark the horse they rode in on
2012-11-18 09:36:57 PM  
1 vote:
I recommend Firebug (and all the dozens of add-ons for it that allow you to do everything under the sun).

Also, any web developer worth their weight doesn't JUST use engine-specific CSS but also the standardised one(s).

-moz-border-radius: 4px
-webkit-border-radius: 4px
border-radius: 4px

/MS has no right to biatch though
//Kings of farking up CSS and HTML
///I use engine-specific nomenclature instead of browser-specific because they're rendering-engine specific...
2012-11-18 01:33:58 PM  
1 vote:

farkeruk: evilmrsock: Front-end guy here. Use better naming conventions.

I do. The problem is other people.

When I'm doing backend stuff, I've got all the tools for working out what the other asshole did. So, I guess my anger is really about front-end tools that don't help me much.

So, anything you can suggest would be helpful.

On chrome or firefox (not sure if you need web developer toolbar installed for firefox but it's fantastically useful anyway so get it), right click and inspect element. I prefer this in Firefox - it puts the style on the right column fully, and also has a 3D view I find useful at times (again, not sure what of this might be in web dev toolbar).

You'll get a style sheet showing every little bit of CSS, and exactly where it came from - what file, what line, etc, and it'll display it in order of priority - the bottom of the list went first (body declaration) and then as it goes to the top it'll show what styles were overwritten later by crossing them out. If it was applied on run-time by script, you won't see what particular script did it but you'll see it on the actual element and you'll see the style it's overwriting being crossed off, which is a nice sanity check.
2012-11-18 09:41:24 AM  
1 vote:
The need to upgrade hardware every 3-4 years because of the new batch of widgetry thats come out of some dev's brain is a never ending source of annoyance. Kudos to a site like Fark for keeping it simple. So many sites just break on contact with anything but the dev's own pet platforms.

Second biggest problem is javascript was never intended to be released. Everything browsers do wrong was based on the original mistake of allowing browsers to run things on the client machine because the server told it to. Fundamentally broken model, pretending to keep state when none exists.
2012-11-17 08:24:16 PM  
1 vote:
Is it just me, or is this one of those rare times that an Ironic tag would actually be relevant and accurate? and we waste an obvious tag on it?
2012-11-17 07:00:03 PM  
1 vote:
Don't you see that multiple vendors coming together to create a cross platform, open source, standards-based html rendering engine is exactly the same as Microsoft trying to kill Netscape by introducing closed source, proprietary extensions that require their own platform to function?
2012-11-17 06:59:56 PM  
1 vote:
Yes, it's a good idea to build websites against standards rather than against what engine happens to be popular.

But no matter how pervasive WebKit gets, there's no indication they're going to halt development and leave it to rot like Microsoft did with IE 6, so the two situations aren't analogous.
Displayed 7 of 7 comments

View Voting Results: Smartest and Funniest

This thread is archived, and closed to new comments.

Continue Farking

On Twitter

Top Commented
Javascript is required to view headlines in widget.
  1. Links are submitted by members of the Fark community.

  2. When community members submit a link, they also write a custom headline for the story.

  3. Other Farkers comment on the links. This is the number of comments. Click here to read them.

  4. Click here to submit a link.