Re: [WSG] media queries can't understand body tag
On 20.09.2011 00:02, tee wrote: Please see this. http://bit.ly/mWvfWC The reason I want to target body tag in media queries is because I don't want to panelize mobile user to load the large background image. I started first with min-width but the result was more problematic, so I switched to max-width. Then you should also reverse the media query sequence. Tested your page locally with reversed mq-order - min-width followed by largest max-width first, and it works fine - switched between 4 distinct backgrounds. regards Georg *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
Re: [WSG] How do you cater to users with disabilities?
On 26.08.2011 17:55, Tedd Sperling wrote: Accessibility is similar to designing sites for different browsers -- it doesn't take extraordinary effort/cost to consider and implement, it only takes knowledge and commitment. +1 *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
Re: [WSG] advertising
On 20.04.2011 10:42, Carl Heaton wrote: HI Everyone, I was just chatting with some of my instructors and I think it would be of semantic value to have a cpc or advertising tag so that paid adverts can be taken out of the documents semantic value. Thoughts? Would be nice from a semantic POV, but probably won't be used much since advertisers will figure out that end-users will target it to hide paid adverts. Georg *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
Re: [WSG] HTML5 v. HTML 4.x
Could someone please clarify this for me. I realise that HTML5 has introduced new semantic elements such as header, aside etc., but does this really increase the expressive power of the markup? Can't the same thing be achieved in HTML 4.x using classes (e.g. p class=header)? I am reluctant to move to HTML5 due to the issue of backwards compatibility. If you're just switching doctype - for a start - there aren't any backwards compatibility issues. After all: the new, short, HTML 5 DOCTYPE is introduced because they needed a compact mode-switch – and for no other reason. Good browsers still don't need it, but IE sure does. http://www.gunlaug.no/contents/wd_additions_34.html Unless you really need any of the new elements right now, it makes sense to just switch to HTML 5 doctype and relax on all else - including backwards compatibility - until the time seems right ... in a few years time. regards Georg *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
Re: [WSG] IE hasLayout - the long and short of it
On 06.01.2011 07:21, David Hucklesby wrote:
Here's my attempt to put a gradient behind some headings. To get
Microsoft's gradient filter to work, I must give the headers layout.
This causes the headings to expand in width in IE6, and to shrink in IE7:
http://thewebwiz.net/temp/has-layout-long-and-short/
Since you're apparently are using an em-sized layout, removing all
present triggers and then adding...
.vcalendar h3 { width: 21em; }
...should trigger hasLayout without negative effects.
Only tested in IETester and Opera, so can't verify gradients.
regards
Georg
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***
Re: [WSG] disallow IE6 to load the main style sheet
On 20.12.2010 21:00, David McKinnon wrote: Sorry Georg, I should have read your article before (re)using that joke! I still not sure I'd spend extra effort to effectively penalise IE6 users. IE6 is not Netscape 4, its CSS support is not that bad. ... I just realised I'm sticking up for IE6! Must be the payback for all the nasty things I've said about it :) David :-) Years ago someone threatened to start a protect IE6 from Georg union. Are you a member..? :-D I'm only presenting my favored solution for splitting IE6 away from the rest so it can be served something it can handle. What others want to do with IE6 once it is separated, is totally up to them. I'm usually quite nice to IE6 users, as can be seen on other pages on my site. All I do is to display a message to IE6 users, urging them to upgrade from their obsolete browser. Some actually accuse me of being too nice to IE6 now and then, so I receive flak from both sides. No big deal. Fixing IE6' bugs so it renders close enough for comfort isn't much of a deal either, although it may be necessary to roll out some of the big artillery to get past its most severe bugs and weaknesses in certain cases. Generally: I see the effort I put into getting IE6 in line, after all the other browsers are served, as good coding practice and something to do when I get bored. regards Georg *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
Re: [WSG] disallow IE6 to load the main style sheet
On 19.12.2010 22:13, David McKinnon wrote: Sounds like you're going to a lot of effort to make the IE6 experince worse than it needs to be. Is this *dis*graceful degradation? ;) David As it says in my article: I've restricted disgraceful degradation to IE6 and older. And, the effort is minimal :-) Not sure if limited styles necessarily make the IE6 experience worse than weak and/or failing styles and corrective measures. As usual that depends on the designer/coder. regards Georg *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
Re: [WSG] disallow IE6 to load the main style sheet
I am finally to begin to stop supporting IE6 starts from 2011 as the usage has fallen below 5%. I don't want the IE6 users to see a broken page due to no special treatment made for the browser, rather, I would like them to see an un-styled page as if the style sheet has switch off. Can this be done? Of course... :-) How to demo here: http://www.gunlaug.no/contents/wd_additions_50.html It is up to you how unstyled IE6 shall present a page. I would give it some. regards Georg *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
Re: [WSG] Order of Tags within head (XHTML)
On 15.12.2010 03:31, Michal Miksik wrote: I was advised by an SEO company that : The Title tag should be the first tag in the HEAD area of the web pages, otherwise search engines may overlook it which will significantly damage the rankings. Someone must be seriously underestimating search engines, or have other reasons for saying that. What is the best practice/order for placing tags withing the head section? The following looks pretty alright to me... - meta(s) - title - links - style(s) - script(s) ...and shouldn't cause loss of attention in search engines or browsers. regards Georg *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
Re: [WSG] Fixed-position menus?
http://thinkplan.org/menupersist.jpg What are peoples' thoughts on this kind of menu? I'm told that IE 6 doesn't support this kind of menu...IIRC, it involves position: fixed; I use fixed menus... http://www.gunlaug.no/main-en.html ...and reconfigure to scrollable on narrow windows - using mediaquery. How key is IE 6, and are people simply not going with this kind of fixed menu? As Thierry says: CSS expressions are evil ... but they'll get the job done in IE6 so I use them anyway :-) regards Georg *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
Re: [WSG] all media queries in one style sheet Vs individually served
The way browsers treating @import isn't the same as @media correct? As mentioned; I haven't tested actual browser-behavior for a long time, but @media and @import are, or should be, handled pretty much the same way by browsers. Either a particular browser supports the media and loads and/or acts on what's inside, or it doesn't support it and ignores the entire CSS file and/or style block. Still some confusing, incomplete and/or incorrect behavior in browsers, so no guarantee. If yes, it seems it's safe to bet that when a desktop browser sees a media queries like these it will ignore link rel=stylesheet media=only screen and (max-width: 480px), only screen and (max-device-width: 480px) / link rel=stylesheet media=only screeand (orientation:portrait) / Yes, BUT, don't trust browsers to treat media in link relations the same as they (should) do @import and @media. Slightly different constructions that serve pretty much the same purpose from different points - pagehead and CSS sheet/block respectively, but which some browsers certainly didn't treat the same only a few years ago. They'll all get there, but some more slowly than others. Or when a Mobile Browser sees this it ignores too (because I don't see a way to print command from any Mobile Browsers that I know of. link rel=stylesheet media=print / Don't know, but print to file may exist on some, to allow for transfers to and printout on another device. Who knows what some upcoming device will be capable of. In the case of @media print, I don't remember where I read it or it's simply just something came up from me due to my flawed understanding, that browser does not load print style sheet until a print request has been made. Sounds logical, but someone else has to to confirm, deny, or correct, on this. FWIW: can't remember having noticed any new fetches from the server when I initiated printing on a site I hadn't visited before, so maybe the browser had already loaded the print stylesheet it used for the printout. rant One thing I'd learned from this targeted audiences, is you can never give/advice/tell them anything more than the little money they paid, or you are asking for trouble because next thing they expect from you is solve every little issue they run into in their sites, including why there are so much white space between each paragraph. And a question like this could be threw at you even a year later. A polite and well-manner customer can be abusive at the same time if you haven't deal with one!/rant Life would be so much easier if we didn't have to deal with clients' expectations... For the time being at least, I don't. Lucky me ;-) regards Georg *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
Re: [WSG] all media queries in one style sheet Vs individually served
Years since I tested what browsers actually did, and much has changed since then. I do prefer to spread styles in logical groups over a few stylesheets, to a certain degree. If nothing else it helps on maintenance and reuse. 1. Will the desktop browser stops loading the above 3 media unless requested? A browser will load everything, as long as it supports, or pretends to support, the link or @import media and queries used. It will put styles to use as needed and supported. 2. If I link each media type individually, does the desktop browser actually load the above 3 style sheets? Same answer. Similarly, will it not better for targeted device not loading two of the media types? If a targeted device loads only the correct style sheets, it will be 2 HTTP requests (one for main style and one for targeted media type) but the file size of each style sheet is significant reduce, and this seems to be beneficial especially for bandwidth concerned mobile devices. Yes? Back in the days we used link and/or @import media and queries as filters to /hack/ browsers - to make them load or not load specific stylesheets. Today we at least try to be a bit more advanced, and use link and/or @import media and queries as filters to /target/ browsers and devices - to make them load or not load specific stylesheets. Reasons may have changed amongst conscious web designers , but browsers are evolving, so too much deliberate filtering at the link and @import stages may mean an existing or future browser/device that can, and should be given a chance to, handle specific styles, won't load them. So, it is my advice that you don't filter more than you have to at the link and @import stages, even if that means slightly fatter stylesheets. *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
Re: [WSG] A simple IE and JS detection method?
On 02.11.2010 04:48, Thierry Koblentz wrote: Using the basic filters you could go this route: http://tjkdesign.com/lab/ie-filters.asp ...which are similar to those I presented earlier ... without all the safeguarding and wrapping i use to keep uninformed people from using such hacks all over the place :-) For version 9+, nothing's sure ;-) That's for sure, which is why I haven't bothered to test hacks for it yet. regards Georg *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
Re: [WSG] A simple IE and JS detection method?
On 29.10.2010 23:33, David Hucklesby wrote: Perhaps you know of a browser-safe filter for IE8? Don't know about safe, but maybe you can find what you need here... http://www.gunlaug.no/contents/styles/target-browser.css regards Georg *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
Re: [WSG] [Spam] :The wisdom? of using q to clear
designer wrote: Thanks to all who replied. However, no-one said don't do this because . . . ?? ...the element is styled to not exist, so it can't do anything... ?? regards Georg *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
