Re: [WSG] Google chrome... Coming very soon... [SEC=UNCLASSIFIED]
people are just freaking over nothing. On Wed, Sep 3, 2008 at 4:07 PM, Blake <[EMAIL PROTECTED]> wrote: > Question: does Chrome actually record your browsing and send that > information back to Google or are people just freaking over nothing? > > On Wed, Sep 3, 2008 at 2:02 PM, Andrew Boyd <[EMAIL PROTECTED]> wrote: > > Tee, > > > > my take on the legal stuff as it may apply to bloggers and other web > content > > providers: > > > http://onblogging.com.au/2008/09/03/does-google-own-my-blog-if-i-post-through-chrome > > > > Cheers, Andrew > > > *** > List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm > Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm > Help: [EMAIL PROTECTED] > *** > > -- - Anton Babushkin *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Google chrome... Coming very soon...
Google Chrome wasn't working for me in the office either, but I think its all due to the firewall and proxy that we have setup here. It couldn't seem to negotiate between the proxy and the installer. I just hooked it up to an outside ADSL connection (my work PC that is), and typing this Email through Chrome right now :) Its a brilliant browser, a true innovation to the way we use the web. Too bad Java and Shockwave don't work on it yet. On Wed, Sep 3, 2008 at 11:43 AM, Blake <[EMAIL PROTECTED]> wrote: > Indeed. We have some very clunky sites and they loaded almost > instantly. I couldn't believe the rendering speed. > > However Gmail won't load on any computers with Chrome on at work (in > fact, I can't sign in to any google services). Is this problem > affecting everyone or is it just our network? If it's affecting > everyone that's pretty massive fail for Google. > > (e-mail sent from Gmail in Firefox!!) > > On Wed, Sep 3, 2008 at 10:15 AM, Jeffery Lowder > <[EMAIL PROTECTED]> wrote: > > > > I know, I tired it on a couple of the more intensive ajax dependent pages > I've been working on and it puts FF to shame. > > If people realize how much faster they can surf the web - this thing is > going to take off big time. > > > *** > List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm > Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm > Help: [EMAIL PROTECTED] > *** > > -- - Anton Babushkin *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] What is the best solution for IE6 png issue?
Yes, true. But there are always special case scenarios. It mainly adopted IE6 as the platform of choice due to the Operating System that they rolled out across the department (Windows XP). There never is a "trully" anything if you look at it from one direction :) On Mon, Aug 4, 2008 at 3:38 PM, Jason Turnbull <[EMAIL PROTECTED]>wrote: > Anton Babushkin wrote: > > > It has absolute truth. I work in the biggest state government > > department in Australia and we have that exact "minus one" policy, > > which means never being at the bleeding edge. > > > There are tons and tons of in house applications that have (sadly) > > been built around the IE6 platform, which would be an absolute > > disaster for the department if IE7 was suddenly rolled out > > If there was truly a 'minus one' policy they would only started developing > for IE6, when IE7 was released > > Regards > Jason Turnbull > > > > > *** > List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm > Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm > Help: [EMAIL PROTECTED] > *** > > -- - Anton Babushkin *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] What is the best solution for IE6 png issue?
It has absolute truth. I work in the biggest state government department in Australia and we have that exact "minus one" policy, which means never being at the bleeding edge. There are tons and tons of in house applications that have (sadly) been built around the IE6 platform, which would be an absolute disaster for the department if IE7 was suddenly rolled out. Its not as simple as upgrading your home PC or your local internet cafe. This is a very similar story to many other companies and deparments Australia and World Wide. The recent embarkement by 37 signals to phase out IE6 is not going to spark anything. They're a small development company and don't have a large customer base around IE6 and don't have a large influence on the general population - rather only on the developmental community. On Mon, Aug 4, 2008 at 2:04 PM, Lewis, Matthew <[EMAIL PROTECTED]> wrote: > > as to say look at the theory of developing specifics for IE6. There is a >> gaining movement around to start phasing out IE6 support - look at >> 37signals, I think they begin IE6 phase out this week or next. They've done >> their maths and taken a gamble. Hopefully it'll spark something. >> [snip...] >> In the end, do you want to spend hours developing hacks for IE6 or just >> nicely push people into an upgrade path? >> >> > OT and not much to do with IE6 .png solutions but instead, the ongoing > support of IE6 aspect of this thread. > > I was advised by a lesser Microsoft management bot that many corporate > organisations have a 'latest minus one' policy, which means only running up > to the previous version of any current browser. This will hopefully mean > that when IE8 is fully released many corporate techs will then upgrade to > IE7, ideally resulting in a bulk upgrade of the costly IE6. > > I hope this has some truth. > > > *** > List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm > Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm > Help: [EMAIL PROTECTED] > *** > > -- - Anton Babushkin *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Should we design for 800x600 screens?
Felix, I think the term "design for" is perhaps a little bit inconsistent in terms of interpretation. Perhaps in this context it was also very badly misinterpreted. When I was referring to "design for" I was more referring to "Accommodate for" which in essence is what fluid layouts are all about. To me "Accommodate for" simply means: - the breaking point at which the page loses its utter most usability, so for example in GMail the usability drastically reduces under a resolution below 800x600 So re-iterate, the page should be as usable as possible; meaning all elements (apart from the content area) should be too large and not too small under resolutions up to 800x600. But in all its essence of what you say - absolutely correct. Web pages should be able to scale gracefully under very small (800x600) to very large (1920x1080) resolutions. On Tue, Jun 10, 2008 at 5:37 PM, Felix Miata <[EMAIL PROTECTED]> wrote: > On 2008/06/10 13:28 (GMT+1000) IceKat apparently typed: > > > Should we still bother > > designing to fit in with 800x600 screen resolutions or is it Ok to just > > design for 1024x768 and not worry about smaller resolutions? > > Never should have been "designing for" either one. To design "for" any > particular resolution means you're designing against all the others. An > "800x600" page on a 2560x1600 screen is little more than a postage stamp, > about 12% in "size" measured in pixels, and definitely an unknown size > measured in inches or mm. > > Some of the resolutions you should NOT "design for" (not an exhaustive > list): > 640x480, 800x600, 1024x768, 1152x864, 1280x960, 1280x1024, 1400x1050, > 1600x1200, 1792x1344, 1856x1392, 1920x1440, 2048x1536, 1024x640, 1280x800, > 1440x900, 1680x1050, 1920x1200, 2560x1600, 1280x720, 1366x768, 1920x1080. > > Erase the concept of screen resolution from your toolbox. Pixels have > nothing > more to do with size than the size of each other. Thinking in pixels is > what > print designers trying to publish to the web think in. The result of such > thinking is billions of magazine pages hosted on the web, not pages > designed > for the users of the fluid web medium that is hosting them. > > Sizing in em means autosizing to the environment, and letting the > environment > figure out how many pixels to get the job done. It's the right way to > design > for the medium and the people who use it. > > http://essays.dayah.com/problem-with-pixels > http://cssliquid.com/ > -- > "Where were you when I laid the earth's > foudation?"Matthew 7:12 NIV > > Team OS/2 ** Reg. Linux User #211409 > > Felix Miata *** http://fm.no-ip.com/ > > > *** > List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm > Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm > Help: [EMAIL PROTECTED] > *** > > -- - Anton Babushkin *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Should we design for 800x600 screens?
For Mobile Browsing you generally take different approaches altogether, especially for WebKit powered phones (the iPhone and the to come GPhone). This is generally because you will be providing completely different navigational structures and really narrowing down on the most important features. Google has "Mobile alternatives" and that is really where developers should be heading when making web pages for Mobile Browsing. Im also wondering how is designing to 800x600 going to make information inaccessible and un-usable? GMail is designed for 800x600 + and is superbly usable. On Tue, Jun 10, 2008 at 3:55 PM, Matthew Hodgson <[EMAIL PROTECTED]> wrote: > what about mobile browsing? > > > > the iphone is having quite the impact on mobile computing and designing to > 800x600 is going to mean you're likely making information inaccessible and > un-usable > > > > designing to a screen size is like designing to one browser > > > > my advice - > > > > 1. profile your users and know who they are, what they want, what they > need, what their online behaviour > > 2. turn profile information into functional and non-functional (design) > requirements > > 3. design to meet those needs > > 4. validate design solutions with those users > > 5. re-assess needs on a regular basis > > > > m > > > -- > *From:* [EMAIL PROTECTED] [EMAIL PROTECTED] On > Behalf Of Anton Babushkin [EMAIL PROTECTED] > *Sent:* Tuesday, 10 June 2008 3:39 PM > *To:* wsg@webstandardsgroup.org > *Subject:* Re: [WSG] Should we design for 800x600 screens? > > I would say Absolutely, absoutely and absolutely! > > My reasoning for this is simple: what about the rest of those users who *don't > browse the internet with the browser in full screen*? As a matter of fact > I'm doing it right now, so thank god GMail scales gracefully, or I probably > wouldn't use it! > > I think the big question is how scalable your web page becomes beyond > 800x600 and that all really depends on the kind of content your web site is > providing. If its something which can be extremelly useful for a Google > Desktop application then perhaps you need to take that into account. If not, > then perhaps rethink your strategy/approach. > > Thats my two cents. > > On Tue, Jun 10, 2008 at 1:28 PM, IceKat <[EMAIL PROTECTED]> wrote: > >> Hi, >> >> I have a question I'd like to poll people about. Should we still bother >> designing to fit in with 800x600 screen resolutions or is it Ok to just >> design for 1024x768 and not worry about smaller resolutions? I know >> applications like Google Desktop make it more complicated and am interested >> to hear people's views. >> >> IceKat >> >> PS- If this has been asked before I apologise and ask if it's possible to >> see mail archives to see the responses. >> >> >> *** >> List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm >> Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm >> Help: [EMAIL PROTECTED] >> *** >> >> > > > -- > - Anton Babushkin > *** > List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm > Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm > Help: [EMAIL PROTECTED] > *** > > -- > NOTICE - This communication is intended only for the person or entity to > which it is addressed and may contain confidential and/or privileged > material. Any review, retransmission, dissemination or other use of, or > taking any action in reliance on, this communication by persons or entities > other than the intended recipient is prohibited. If you are not the intended > recipient of this communication please delete and destroy all copies and > telephone SMS Management & Technology on 9696 0911 immediately. Any views > expressed in this Communication are those of the individual sender, except > where the sender specifically states them to be the views of SMS Management > & Technology. Except as required by law, SMS Management & Technology does > not represent, warrant and/or guarantee that the integrity of this > communication has been maintained nor that the communication is free from > errors, virus, interception or interference. > > *** > List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm > Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm > Help: [EMAIL PROTECTED] > *** > -- - Anton Babushkin *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Structuring CSS
Interesting to hear. I will do a formal test on our network sometime when I get the chance and report on my findings as well. Out of curiosity, it wasn't an actual physical stop watch was it? Its far less error prone to use something like the Net tab of Firebug or an external plugin like "Charles" which can show you how fast segments are downloading etc. On Tue, Jun 10, 2008 at 3:41 PM, Peter Ottery <[EMAIL PROTECTED]> wrote: > Anton wrote... > - > In regards to "I'm guessing this sort of structuring comes at a cost > because a number of requests need to be made to the server." this is > generally untrue. In principle this is exactly how download > accelerators work. They split a large file into smaller segments and > sent multiple requests. Since the browser environment is completely > multi-threaded it should actually boost performance. (Note: I am not > 100% certain if this is the fact, but there is no evidence to suggest > otherwise either). > - > > If its a small site, with not much traffic I think you'd be hard > pressed to notice the difference. For large news sites that get > smashed with traffic, I've sat there with a stopwatch and timed the > difference (over different speed connections from dialup to broadband) > between separate css files, and all in 1. And just having 1 file is > definitely faster. > > in some cases it would bring the initial [1] load time [2] from > something like 6 seconds down to 3 or 4. and then bringing all the css > into the of the page rather than a linked file chopped another > second off. > > as i said - only applicable if extreme performance/optimisation is an > issue - but it *does* make a difference. > > [1] - with an empty cache > [2] - the time taken for the page text to appear, the page might > continue loading for 10 or so seconds after this so loading in pics > etc. mileage varies > > pete > > > *** > List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm > Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm > Help: [EMAIL PROTECTED] > *** > > -- - Anton Babushkin *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Should we design for 800x600 screens?
I would say Absolutely, absoutely and absolutely! My reasoning for this is simple: what about the rest of those users who *don't browse the internet with the browser in full screen*? As a matter of fact I'm doing it right now, so thank god GMail scales gracefully, or I probably wouldn't use it! I think the big question is how scalable your web page becomes beyond 800x600 and that all really depends on the kind of content your web site is providing. If its something which can be extremelly useful for a Google Desktop application then perhaps you need to take that into account. If not, then perhaps rethink your strategy/approach. Thats my two cents. On Tue, Jun 10, 2008 at 1:28 PM, IceKat <[EMAIL PROTECTED]> wrote: > Hi, > > I have a question I'd like to poll people about. Should we still bother > designing to fit in with 800x600 screen resolutions or is it Ok to just > design for 1024x768 and not worry about smaller resolutions? I know > applications like Google Desktop make it more complicated and am interested > to hear people's views. > > IceKat > > PS- If this has been asked before I apologise and ask if it's possible to > see mail archives to see the responses. > > > *** > List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm > Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm > Help: [EMAIL PROTECTED] > *** > > -- - Anton Babushkin *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Structuring CSS
The way I structure my CSS is very much like you said - taking the Software Development principles of Object-Oriented programming, and is pretty much inline with what everyone else has said. I generally break my CSS up to the following categories: - reset.css : Reset all browser defaults. Gecko, WebKit and Explorer based browsers all have different presets (lists are just one example) so this is very cruicial in making the look and feel consistent. - skeleton.css : Defines my main architectual skeleton, i.e. will it be a three-column layout? a fluid layout? a fixed width layout? This essentially allows me to reuse the CSS very efficiently. I can also switch between layouts very quickly. After that I generally make a judge call on how complex the organisation is and how the CSS might or will be overriden. In a large and complex organisation, that generally consists of smaller individual business I generally split the CSS up even further into the following categories: - content.css - typogaphy.css - forms.css - tables.css I might even go further by splitting the positioning away from the colour. It really depends on how confident the people within each different business are with CSS. This generally allows many people; with varying degree of confidence and skill level to make small changes which might be necessary for their particular business/branch. In regards to "I'm guessing this sort of structuring comes at a cost because a number of requests need to be made to the server." this is generally untrue. In principle this is exactly how download accelerators work. They split a large file into smaller segments and sent multiple requests. Since the browser environment is completely multi-threaded it should actually boost performance. (Note: I am not 100% certain if this is the fact, but there is no evidence to suggest otherwise either). In the end you should also generally use a bridge file to connect all the CSS together. Hope that answers your question. On Tue, Jun 10, 2008 at 9:00 AM, James Jeffery < [EMAIL PROTECTED]> wrote: > Lets have it. How are you guys structuring your CSS files? > > I have been having a think about this over the last few days. My research > attempts have failed because most the articles i came across were outdated - > so i tend not to trust them. > > One method i thought about (not sure if it's been coined) is one based on > Software Engineering principles, obeying rules such as decoupling et cetera. > Maybe by using these principles modules can be included by importing the > needed CSS file (and path) in the root CSS file. > As i am writing this i am certain CMS systems use this method of > structuring CSS. > > I am sick to death of having to over comment my CSS files to find what it > is i'm looking for. I would much rather break up my layout into semantic > chunks and create a seperate CSS file for each chunk (i.e navigation, > content, footer). > > I'm guessing this sort of structuring comes at a cost because a number of > requests need to be made to the server. > > Regards > > James Jeffery > > *** > List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm > Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm > Help: [EMAIL PROTECTED] > *** -- - Anton Babushkin *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Breadcrumbs showing organisational structure and usability
ibrary > Current page >>> >>> The only thing that's going to change is the current page. To me, >>> that's not a breadcrumb trail at all. >>> >>> Am I wrong in my thinking? Is this a common usage? How does this >>> benefit the user at all? >>> >>> I'm questioning it because of usability issues, which is how I tie it >>> in with web standards. If this is considered off-topic, I apologise, >>> and replies should come directly to me rather than the list. >>> >>> thanks, >>> lib. >>> >>> >>> *** >>> List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm >>> Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm >>> Help: [EMAIL PROTECTED] >>> *** >>> >>> >>> >>> >>> -- >>> -- >>> Steve 'Doc' Baty B.Sc (Maths), M.EC, MBA >>> Principal Consultant >>> Meld Consulting >>> M: +61 417 061 292 >>> E: [EMAIL PROTECTED] >>> >>> UX Statistics: http://uxstats.blogspot.com >>> >>> Member, UPA - www.upassoc.org >>> Member, IA Institute - www.iainstitute.org >>> Member, IxDA - www.ixda.org >>> Contributor - UXMatters - www.uxmatters.com >>> *** >>> List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm >>> Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm >>> Help: [EMAIL PROTECTED] >>> *** >>> >> >> >> >> *** >> List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm >> Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm >> Help: [EMAIL PROTECTED] >> *** >> >> > > > -- > -- > Steve 'Doc' Baty B.Sc (Maths), M.EC, MBA > Principal Consultant > Meld Consulting > M: +61 417 061 292 > E: [EMAIL PROTECTED] > > UX Statistics: http://uxstats.blogspot.com > > Member, UPA - www.upassoc.org > Member, IA Institute - www.iainstitute.org > Member, IxDA - www.ixda.org > Contributor - UXMatters - www.uxmatters.com > *** > List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm > Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm > Help: [EMAIL PROTECTED] > *** > -- - Anton Babushkin *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Breadcrumbs showing organisational structure and usability
Hi lib, The organization that I am part of uses breadcrumbs, however they're used to display where the user has been and one link to indicate the top level. I think in terms of usability they can help a user associate themselves with your structure if they're really searching for something. They're also typically used as a last bail option when all else fails (including the Back button). To be honest, in your case they don't benefit the user in any sort of way except perhaps help them understand how your corporate structure works (but who actually cares?). On Fri, Jun 6, 2008 at 4:45 PM, libwebdev <[EMAIL PROTECTED]> wrote: > Hi folks, > > My organisation manages around 7000+ pages for 100s of departments, > using a CMS. Mine is the only department outside the CMS, just because > we can. > > We have been persuaded (read: bullied) to redesign our header to > exactly match that of the parent organisation. I have no problem with > that per se, but theirs includes breadcrumbs, and we don't want 'em. > > I'm wondering what the consensus is here on their usefulness. I've > always been under the impression that the purpose of breadcrumbs was > to indicate to the user where they had been. However, the ones we are > being urged to implement do no such thing; they simply display our > organisational structure. This means that on every one of our 200-odd > pages, the breadcrumbs will appear like so (we are the library): > > Parent Org > Clinical Services > Library > Current page > > The only thing that's going to change is the current page. To me, > that's not a breadcrumb trail at all. > > Am I wrong in my thinking? Is this a common usage? How does this > benefit the user at all? > > I'm questioning it because of usability issues, which is how I tie it > in with web standards. If this is considered off-topic, I apologise, > and replies should come directly to me rather than the list. > > thanks, > lib. > > > *** > List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm > Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm > Help: [EMAIL PROTECTED] > *** > > -- - Anton Babushkin *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] tools for IE
Nice tools. IE8 comes with a web developer addon, and although I don't quiet think its as good as Web Developer or Firebug, it does a pretty good job. On Sat, May 31, 2008 at 8:05 AM, Thierry Koblentz <[EMAIL PROTECTED]> wrote: > Dev Toolbar type for IE: > http://www.debugbar.com/ > > And a very interesting concept: > http://www.my-debugbar.com/wiki/IETester/HomePage > > > -- > Regards, > Thierry | http://www.TJKDesign.com > > > > > > > > > *** > List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm > Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm > Help: [EMAIL PROTECTED] > *** > > -- - Anton Babushkin *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Marking up company logo
I concur. Having it as a is a much better way of dealing with it rather than having it as an image or . To me its less about SEO and much more about usability. People don't really care about your company, they're simply after the major headlines. Having a company logo take up the majority of the real-estate is less user-friendly and much more spammy. Maybe I am just a minimalist. On Thu, May 29, 2008 at 2:32 PM, Jens-Uwe Korff < [EMAIL PROTECTED]> wrote: > > The H1 should be used for the most important heading, usually the name > of the page > > I second that. > > We used to have lots of logos in s too, and after a thorough SEO > discussion we changed that to a . > > The now holds the page title. > > > Cheers, > > Jens > > The information contained in this e-mail message and any accompanying files > is or may be confidential. If you are not the intended recipient, any use, > dissemination, reliance, forwarding, printing or copying of this e-mail or > any attached files is unauthorised. This e-mail is subject to copyright. No > part of it should be reproduced, adapted or communicated without the written > consent of the copyright owner. If you have received this e-mail in error > please advise the sender immediately by return e-mail or telephone and > delete all copies. Fairfax does not guarantee the accuracy or completeness > of any information contained in this e-mail or attached files. Internet > communications are not secure, therefore Fairfax does not accept legal > responsibility for the contents of this message or attached files. > > > *** > List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm > Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm > Help: [EMAIL PROTECTED] > *** > > -- - Anton Babushkin *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] print css crashing ie6
Gallagher, Robin skrev: Hi I've got a 3-column css page that crashes IE6 when I try to print or print preview. Can anyone suggest a possible cause? Hard to say without access to the CSS code. Have you got an URL? /Anton ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help **
Re: [WSG] My Style Switcher...
Sounds pretty cool.
I'm curious though, what's the file size of all that php in the css, as opposed
to actually handling 4 separate css files for color that can @import the main
body/text styles from a fifth master file?
It sounds really big and fancy, but for a style switcher I'm just wondering how
efficient all that work is?
Sorry if I sound negative, I don't mean to... I'm just not really a fan of style
switchers unless it has a distinct advantage of adjusting readability/usability
for the visitor.
Although, to your advantage, I love kick-ass php writing.
Anton
Quoting Chris Stratford <[EMAIL PROTECTED]>:
> *Hey WSG,*
>
> I have just begun re-development of neester.com once again.
> This time because my server switched Magic Quotes on... Which is good!
> But all my old scripting had addslashes etc... and it just became really
> dodgy etc...
> It was a good excuse to redevelop it again.
>
> If you goto www.neester.com you will see a grey page.
> I have used my own styleswitcher which I think is very efficent and well
> - its pretty cool how it all works.
> I will explain it here now - and I will write an article when I am
> finished with the site...
> BTW I know I could of used Lorium Ipsum - but Google will get annoyed
> and think its /latin/, happened before.
>
> Ok.
> What happens is, once you load the page - the PHP inside index.php sets
> the stylesheet location in the HEADER to:
> > > link rel="stylesheet" href="/styles/d_index_default.css"
> title="Neester.Com | Default Style" media="all" type="text/css"
>
> See how the location is d_index_default.css
>
> Well, that basically means, it loads the default stylesheet, for the
> index page, with the colour: default...
> If you click on a different style on the page, say Green...
> that will then become:
> > > link rel="stylesheet" href="/styles/d_index_green.css"
> title="Neester.Com | Default Style" media="all" type="text/css"
>
>
> Each page also changes the link...
> eg - if i had the contact page working.
> The link inside that would be:
> > > link rel="stylesheet" href="/styles/d_contact_default.css"
> title="Neester.Com | Default Style" media="all" type="text/css"
> or if you are still using green
> > > link rel="stylesheet" href="/styles/d_contact_green.css"
> title="Neester.Com | Default Style" media="all" type="text/css"
>
> Now I dont actually have 100,000 stylesheets for all these.
> I am using .htaccess to redirect these connections to a single PHP CSS
> file...
>
> I cant include the whole file here, but here is an algorithm of how it
> works is below...
>
> The PHP loads with about 100 variables (colours, margins, paddings,
> background images, fonts etc...)
> Then the PHP has a "switch" function - which deterimines WHICH colour
> you are loading...
> Then it resets some of the 100 variables - to suit that style...
>
> THEN it echo's the DEFAULT styles to the browser...
> Then it has another SWITCH, which it echo's only that PAGES RELEVANT
> styles...
> eg:
> contact page would have:
>
> #contact_form input,#contact_form select,#contact_form textarea
> {
> blah...
> }
>
>
>
> SOO
> In effect.
> The browser sees 4 stylesheets per page if you go through each of the
> styles...
> And it will cache them too - because they actually have a real path
> (.htaccess just modifies it when it gets to the server)...
> So it will run asif I have 100 stylesheets...
> but in effect, i only have one!
>
> adding those 4 styles has been a breeze.
> I just added about 20 lines to each of the STYLES SWITCH function points...
> And yeah - because you only edit the styles you want to change.
> The rest can stay default (margins for example...)
>
>
> *If you are more interested, I can send you the PHP code for this.
> I dont mind if other people use this method - I would like it if you
> gave me credit.
> but yeah.
>
> I havent seen it used anywhere else - but then again - I didn't really look.
> if you have seen this method used somewhere else - please post some links...
> Cheers!
>
> *Hope that wasnt too long...
> And I hope it is easy to understand - and someone out there learnt
> something they might use...
> *
> *--
>
> Chris Stratford
> [EMAIL PROTECTED]
> http://www.neester.com
>
> **
> The discussion list for http://webstandardsgroup.org/
>
> See http://webstandardsgroup.org/mail/guidelines.cfm
> for some hints on posting to the list & getting help
> **
>
>
**
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list & getting help
**
Re: [WSG] Dotted line.
The attributes seem swapped to me, it should go {size | type | color}.
You can also shorten the color to three letters to replace the double sets, like
so:
dt a:hover {
border-bottom: 1px dotted #FC0;
}
Quoting Bennie Shepherd <[EMAIL PROTECTED]>:
> This is what is giving the dotted line...
>
> dt a:hover {
> border-bottom: 1px #FFCC00 dotted;
> }
>
>
> --
> Get Firefox Browser
> http://www.spreadfirefox.com/?q=affiliates&id=6908&t=58
>
> Bennie's MIDI Page
> http://bennieshepherd.com/
>
> Athens, Georgia, Relay For Life
> http://www.athensrelay.net/
>
> Montrose, Colorado, Relay For Life
> http://montroserelay.com/
>
> Grand Junction, Colorado, Relay For Life
> http://grandjunctionrelay.org
>
> LZ Friendly Veterans Org
> http://lzfriendly.org
>
>
> **
> The discussion list for http://webstandardsgroup.org/
>
> See http://webstandardsgroup.org/mail/guidelines.cfm
> for some hints on posting to the list & getting help
> **
>
>
**
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list & getting help
**
Re: [WSG] Validator error
you got it. This link from the w3 might help (I hope): http://www.w3.org/TR/REC-html40/sgml/entities.html I try to stick with the alpha-based entities anyway, so that when I look at it later, I can easily recall which character I used. > I don't have an answer, but can I add to the question? > > I get 'non-SGML character' warnings (NB warnings, not errors) when I > use, say, & instead of & to escape an ampersand. Which syntax > fpr character entities is correct? Or does it depend on the charset > specified in the Content-Type? I understand that & is Unicode, but > I always (well, usually) specify iso-8859-1. Is this why I'm getting > these warnings? Should I stick to the alpha-based entity descriptions > for iso-8859-1? ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help **
Re: [WSG] Mac IE 5.2 and horizontally presented s
I'm running into a problem with the presentation of my primary navigation in Mac IE 5.2. [..] http://www.capstrat.com/development/cs2004/template4.html First, try to use div#navigation ul instead of div#nav-primary ul, if that's what you want to control (at least it becomes much easier to read that way ;) and try to indent your code approprietly. Second, I think that your main problem is the lack of a width attribute to your floats. Also IE5/Mac prefer floated items instead of inlined, but that may vary. Try this first and come back if you still encounter problems. cheers, /Anton -- What your lacks, your compensates. * The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help *
Re: [WSG] small gap
I'm sorry to ask this question but I've been looking at this page for too long and I can't see why there is a small gap between the top nav and the content. I think it's due to the padding-bottom in the #current selector. Try to apply the padding to the links just once, then add current-specific stuff (like color:white) cheers, /Anton -- What your lacks, your compensates. * The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help *
[WSG] webstandardsgroup.se registered - feedback wanted
Hi, I just registered webstandardsgroup.se, a potential Swedish sister-site to webstandardsgroup.org. Got some ideas for it already, would be glad to recieve others too (preferably off-list). I'll keep you posted later on when ideas start to take more shape. cheers, /Anton -- What your lacks, your compensates. * The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help *
Re: [WSG] Problems in Mac IE 5.2
Could someone please tell me if I need some special "hack" for Mac IE or if there is a solution at all? I think I know the answer to this one (as I just spend hours on the same type of IE5/Mac dilemma). There seems to be a bug in IE5/Mac involving "inherited clearing" (in lack of a better term for it). So, your "clear: both" on #container messes things up for all floats inside it. Get rid of the clear on the #container div and try to 1) make your menu as exact height-wise as you can (so you don't need it) or 2) add another kind of "clearer" before it. Hope that helps. /Anton -- What your lacks, your compensates. * The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help *
Re: [WSG] Some links for reading...
CSS: The Good, the Bad, & the Ugly: http://www.stopdesign.com/present/sxsw2004/goodbad/ Well, I still think this method rocks: http://levin.grundeis.net/files/20031217/test.html (found at: http://levin.grundeis.net/files/20031203/ir.html) cheers, /Anton -- What your lacks, your compensates. * The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help *
[WSG] Filtering out Safari 1.2 frmo Mozilla?
Hi, could someone please help me out here. I need to feed Mozilla
with this code:
html[xmlns] > body #chronique div.title { margin: -1.5em 0 0 20px; }
...but I need to reset the top margin for Safari 1.2, is there any
way this can be done? I just noticed (rather late, I know ;) that
Safari 1.2 eats the html[xmlns] selector but hasn't got Mozilla's way
of handling list-position:inside, so my Magazine page triggers a
"buggy" appearance in the otherwise wonderful OS X browser..
TIA,
/Anton
--
What your lacks, your compensates.
*
The discussion list for http://webstandardsgroup.org/
*
Re: [WSG] CSS and PhpNuke
Does anyone have any examples of well implemented CSS with this program? You can take a look at: http://www.stockholmsfria.nu/, it's the online version of a Swedish newspaper I'm working with. I've done the CSS coding and the phpNuke hacking which, to be honest, is a pain in the ___. The whole OpenTable()/CloseTable() abuse is sparyed all over the code (inserts eye candy for fake borders etc) and ed & eakfast, unquoted attributes and lack of semantics is also very common. Needless to say I didn't chose this CMS ;) but just continued an old project, trying to make the best out of it. I could give you some more tips off-list if you decide to go with it, but it's definately coded by geeks, for geeks, and mainly as a community-forum (with private upload areas, my stock quotes, etc) and not an ideal CMS, if that's the main thing you want. cheers, /Anton -- What your lacks, your compensates. * The discussion list for http://webstandardsgroup.org/ *
Re: [WSG] "Dodging CSS Hacks" Tutorial
http://web.theward.net/dodgingcsshacks.html Technically, Trident has got little (or nothing?) to do with CSS parsing. I found a post from "liorean" at css-d explaining this: "Just as a note, Trident is the rendering engine of ie/w. It is not the XML, the HTML/tagsoup or the CSS parsing engine; nor is it the scripting engine or external parsing system. It is the rendering engine, outsourcing the parsing and foreign object handling to other systems or engines. It seems that Trident has been roughtly the same since ie4, with the changes taking place mostly in the other engines, Trident only changing when really required to, in order to be able to render what it is handed from the others." Further info about Trident is way beyond my skills and, perhaps, beyond the goal of what you're trying to say with your web page :] - I just found it interesting and it could help in correcting erroneous info/rumors about what Trident is/is not. cheers, /Anton -- What your lacks, your compensates. * The discussion list for http://webstandardsgroup.org/ *
[WSG] DOM scripting
Hi, I just updated my blog at: http://andreasson.org/, using some DOM scripting à la Flash. Please give me some feedback, I've never done this kind of stuff before (and haven't tested it a lot yet). cheers, /Anton - got to get some sleep now.. -- What your lacks, your compensates. * The discussion list for http://webstandardsgroup.org/ *
Re: [WSG] A few quick links...
A strangely unstyled page, but some excellent concise info on accessibility Heh, I like this one: WWW ;) Otherwise a good read. /Anton -- What your lacks, your compensates. * The discussion list for http://webstandardsgroup.org/ *
[WSG] Background PNGs in IE/Win?
Anyone knows of the support for background (24bit) PNGs in IE/Win? I've seen PNGs show up with a gray box around it, but does this apply when using them in background-image: as well? TIA, /Anton -- What your lacks, your compensates. * The discussion list for http://webstandardsgroup.org/ *
[WSG] Cool color picker
http://www.pixy.cz/apps/barvy/index-en.html Very nice... /Anton -- What your lacks, your compensates. * The discussion list for http://webstandardsgroup.org/ *
RE: [WSG] Calendar Day Highlighting
Given the recent discussion on definition list, maybe you could build it with those as an alternative? Well, thanks for the suggestion but as I know what happens with definition lists in e.g. Google (try search for "define: css" and you'll see), I wouldn't want my calendar being indexed as "Definitions of Monday on the Web:" and "Meeting with friends at local pub" as a description... I might be stubborn about this, but I just can't find The Argument for switching to s instead of, well, wrapping it in a or something. cheers, /Anton -- What your lacks, your compensates. * The discussion list for http://webstandardsgroup.org/ *
[WSG] Calendar Day Highlighting
Hi all, I throw together a simple "calendar" that highlights each day on :hover, hope you find it intresting (given the tight code): http://standardice.com/experimental/calendarhighlighting.html cheers, /Anton PS. I was inspired by the Flash calendar at http://www.vcc.com.my/calendar/index2.cfm and I'll try to mimic it even further ;) -- What your lacks, your compensates. * The discussion list for http://webstandardsgroup.org/ *
Re: [WSG] A few links...
While the archive section is partially helpful, any useful link posted to WSG should also be added to our resources section. Is there any way some skillful coder here could hack up a script to parse the list emails, strip out all links, present them in a "recent links sent to wsg-list" kind of list, with some buttons like "add me to wsg resource archive" (if the user finds it valuable)? Just an idea that could make check-ins a funnier thing to do, me also being a "slacker" ;) cheers, /Anton -- What your lacks, your compensates. * The discussion list for http://webstandardsgroup.org/ *
Re: [WSG] AudioSite template - almost there ...
Write onload instead of onLoad (yes, it's ridiculous.. ;) cheers, /Anton -- What your lacks, your compensates. * The discussion list for http://webstandardsgroup.org/ *
Re: [WSG] AudioSite template - almost there ...
If I'm right, it's just a matter of making the L in "onLoad" lowercase. remember, all attributes must be in lowercase. This includes Javascript calling functions (eg, onMouseOver => onmouseover) oops, sorry :] Note to self: _read_ the mail before hitting reply, bummer.. /Anton -- What your lacks, your compensates. * The discussion list for http://webstandardsgroup.org/ *
Re: [WSG] styling hr tags
I can never understand why tags made it into the XHTML spec, as they are pretty much presentation-only, not structure. is supposed to mean "change of topic" structurewise. cheers, /Anton -- What your lacks, your compensates. * The discussion list for http://webstandardsgroup.org/ *
[WSG] Nokia ignores XHTML DOCTYPES?
Just read this one and found it quite shocking: http://blog.outer-court.com/archive/2004_01_05_index.html#107329348165573660 How come it IGNORES the CSS if it's not a Nokia-only DOCTYPE[1] or a XHTML Basic[2] one? Wouldn't even XHTML Transitional work, or did I miss something? Weird.. cheers, /Anton [1] http://www.wapforum.org/DTD/xhtml-mobile10.dtd";> [2] http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd";> -- What your lacks, your compensates. * The discussion list for http://webstandardsgroup.org/ *
Re: [WSG] do people still use bookmarks?
I don't know about you guys, but Word Documents, Bookmarks and URI namespace rules takes a lot of space on this list now, and I'm drowning.. Could we all please be a little more brief when discussion thos (OT) issues, ok? TIA, /Anton -- What your lacks, your compensates. * The discussion list for http://webstandardsgroup.org/ *
Re: [WSG] ex as a font size
Anyone have any experience using this? I use it instead of em's from time to time, mostly when defining widths and I know I won't be using capital letters. cheers, /Anton -- web standards guy #1: nice one, huh? ok, now your turn... web standards guy #2: ok... how about this one: colspan=9. web standards guy #1&2: phfff-GAH-AHA-HAHA-HOHO-HO-HIHI!!! * The discussion list for http://webstandardsgroup.org/ *
Re: [WSG] Another full CSS site
Another full css site goes live: Is there a site dedicated to listing all these "switchers" in the works..? cheers, /Anton -- web standards guy #1: nice one, huh? ok, now your turn... web standards guy #2: ok... how about this one: colspan=9. web standards guy #1&2: phfff-GAH-AHA-HAHA-HOHO-HO-HIHI!!! * The discussion list for http://webstandardsgroup.org/ *
RE: [WSG] A few interesting articles...
tags - you get a "site navigation" bar under the location bar with words like "home", "help", "index", "search", etc... In iCab too, IIRC ;) /Anton -- What your lacks, your compensates. * The discussion list for http://webstandardsgroup.org/ *
[WSG] Mac and screen readers
No screen reader software for the mac platform - a change is on its way? http://www.businessweek.com/technology/content/nov2003/tc20031112_9773_tc056.htm cheers, /Anton -- What your lacks, your compensates. * The discussion list for http://webstandardsgroup.org/ *
[WSG] Site check: Listamatic entry (to-be)
Hi all, Got some ideas I just had to try: - How about using the Listamatic #current list item as a visial identifier, placed elsewhere in the document? - Can one create a nice-looking :hover effect with letter-spacing when using floats, since text is not centered? I put it together at: http://standardice.com/experimental/separatecurrent.html ...but I haven't tested in anything more than IE5/Mac or Mozilla 1.2.1 yet. Could someone please email me an IE/Win report of some kind? Browsercam boggs down my modem line and I'm running out of unused mail aliases... ;( cheers, /Anton -- What your lacks, your compensates. * The discussion list for http://webstandardsgroup.org/ *
[WSG] Dave Hyatt, Safari and XUL/XAML
http://weblogs.mozillazine.org/hyatt/archives/2003_10.html#004257 Probably his longest blog entry ever.. :] /Anton -- What your lacks, your compensates. * The discussion list for http://webstandardsgroup.org/ *
Re: [WSG] Some light reading...
1. Sites built to web standards do not have to be full-CSS. While it is a great goal, it is not essential. You can use hybrid layouts with a basic table grids to hold the elements in place and all other presentation driven by CSS. Exactly.. But I don't get his "can't look in the source to find out how it's gonna look like" attitude[1] against 's. Seems awkward to me... I mean, why bother having clever source order then? I'd like to add though, as he mentions speed of pages, that for me (sitting on a PowerBook 3400 at the moment) my modem is the bottleneck for many -based sites, but my graphics card(!) is the biggest bottleneck for CSS-heavy sites... cheers, /Anton [1] "You essentially make it harder to figure out where things go in design view, and on top of that, maintain it in the first place." PS. He also notes: "What's really stupid is that these non-visual browsers aren't smart enough to figure out what the words mean or have some idea what they pertain to? There is a spell checker and a GRAMMER [sic!] checker in Microsoft WORD." Oh, there is? ;) -- What your lacks, your compensates. * The discussion list for http://webstandardsgroup.org/ *
Re: [WSG] Some light reading...
Maybe already posted(?): http://www.decloak.com/Products/Dreamweaver/NestedTemplates/TablesOrLayers.aspx (found at saila.com) /Anton -- What your lacks, your compensates. * The discussion list for http://webstandardsgroup.org/ *
[WSG] HTML 4.01 vs XHTML 1.0 ?
Hi all, What do you think about this read: http://hixie.ch/advocacy/xhtml ? /Anton -- What your lacks, your compensates. * The discussion list for http://webstandardsgroup.org/ *
RE: [WSG] PHP & MySQL CMS that adheres to Web Standards [Virus checkedAU]
* Anyone has ideas how to get the semantic message through too? Like, != and here's why: ... Seems to be a great dilemma and not only a parsing/validation issue :/ cheers, /Anton -- What your lacks, your compensates. * The discussion list for http://webstandardsgroup.org/ *
[WSG] I won! :)
http://www.fifteen.be/ I'm just a little afraid I may find some errors in my entry now when looking at it again.. After all it was about a month ago that I sent it in and I've learnt a lot since, especially about font-sizing.. :] cheers, /Anton -- What your lacks, your compensates. * The discussion list for http://webstandardsgroup.org/ *
RE: [WSG]Forms and definition lists
You can have multiple s to your s. Yes, this should be used (again IMO) when a word or a phenomenon or similar can have different meanings (depending on how it's pronounced even).. I'm all for openining up semantics, I just don't see the form field thingie as a good enough reason.. cheers, /Anton - gotta rush for the pub quiz.. -- What your lacks, your compensates. * The discussion list for http://webstandardsgroup.org/ *
Re: [WSG]Targetting CSS at IE 5 and 5.5 only
One thing I did notice about your browser targeting was that it picks Konqueror as Mozilla - I think that was with 3.1.4 and 3.2 alpha which includes lots of the Safari fixes. Yeah, at the moment I've renamed that column to "Moz/KHTML" since I don't know of any (validating) hacks that filter these three out. Maybe I could use a Mozilla-only thingie but there are IMO very few occasions one need to distinguich between at least Moz and Safari renderings (I know one[1] though ;), so maybe a Konqueror column (for older versions than 3.2) would be appropriate? But then again, the Konq folks upgrade their stuff veery often, it seems to me.. I guess this is one reason I started adding a version number to that page ;) /Anton [1] http://standardice.com/experimental/test.html -- What your lacks, your compensates. * The discussion list for http://webstandardsgroup.org/ *
RE: [WSG]Forms and definition lists
I would rebut with this: the HTML 4.01 specification says that a dl could be used for pairings other than definitions, citing a script (character/speech pair) as an example. Well, yes. But I could understand that if e.g. the e-mail address field had a specified value that told me what my e-mail address was. In real life though, I define this as I want which makes the "definition" very loose. In fact, I could fill in Hamlet's e-mail, or his Actor's mother's (to use the theatre metaphore) - that doesn't "define" "Your E-mail:" very much, IMHO, since it's up to you to tell the truth or not.. my .02¤ /Anton -- What your lacks, your compensates. * The discussion list for http://webstandardsgroup.org/ *
Re: [WSG]Targetting CSS at IE 5 and 5.5 only
http://tantek.com/CSS/Examples/midpass.html
I'm using:
* html p { color: maroon; } <--- which IE5 & 6 understands
* html p { co\lor: red; } <--- which IE6 then overrides (not IE5/Win though)
/Anton
--
What your lacks, your compensates.
*
The discussion list for http://webstandardsgroup.org/
*
Re: [WSG]Bottom Aligned Div Tags
Hi Adam,
#header {
position: absolute;
left: 0px;
right: 0px;
top: 0px;
}
You shouldn't actually use left and right together this way, try
instead to use a combination of only one x-value and one y-value.
#page_content {
Also, try to avoid underscore in class names, use "-" instead.
There's an article at DevEdge [1] somewhere about this, IIRC.
#footer {
position: absolute;
left 0px;
A typo here: no ":" after left, maybe you've spotted this already.
To your question though:
Because the footer is going to contain random quotes, I don't really like my
"50 pixel" method of positioning the footer, and the page content can still
overlap with the footer. Does anyone know of a better way?
If I get it right, what you want is about the same thing as one gets
when removing all the position: absolute attributes, except that you
want the #footer to reach the bottom (minus 50px) when the body
height is smaller than the viewport, is that right? And if the body
grows, it should start pushing down the #footer to the very bottom of
the page and not have it "glued" there anymore, right? Unfortunately,
I don't think this is possible without using javascript or maybe some
IE/Win-only tricks.
Remember, when using absolute positioning you break the flow of your
document. In your example code, the therefore has no height at
all, since nothing actually "flows" inside it. Instead, everything is
positioned with regard to the viewport. The #footer which will
therefore ignore the #page_content, even if its content grows, again
since absolute positioning disregards the flow of elements. What's
more, displaying absolute positioned elements is for the browser
about the same thing as displaying a table-based layout - it doesn't
show you any content until it's all done. Of course it's a lot better
semantically speaking, but not "performance-wise" as you can't start
reading as its content loads. You might have guessed by now that I'm
a fan of flowed content rather than positioned, huh? :)
cheers,
/Anton
[1] http://devedge.netscape.com/
--
What your lacks, your compensates.
*
The discussion list for http://webstandardsgroup.org/
*
[WSG]More mimics
Just to drop a note that I've added a few more magazine mimics today, one of which I'm especially proud of (La Cronicle). It's using the list-style-position: inside (combined with paddings) to colorize the background of the list number, which normally is very hard to do. Check it out at: http://standardice.com/experimental/magazines.html Again, I'd love to hear from people with Operas or IEs/Win if there are any problems (since Browsercam won't scroll-capture for me it seems ;) I also started using XHTML Strict, hope that won't mess up things (but it won't since I have no target="" attributes or block items within 's, right?) cheers, /Anton -- What your lacks, your compensates. * The discussion list for http://webstandardsgroup.org/ *
[WSG]Image replacements
Did I miss something or why is the FIR[1] and LIR[2] methods touted as being so cool? I thought "visibility: hidden" did the job, no? Since it differs from "display: none" in not removing the block from the page. cheers, /Anton [1] http://www.stopdesign.com/articles/css/replace-text/ [2] http://www.kryogenix.org/code/browser/lir/ -- What your lacks, your compensates. * The discussion list for http://webstandardsgroup.org/ *
[WSG]Magazine imitations, Target-a-browser
Two things: 1) I've been doing some imitations of magazines once in a while and have now collected them at: http://standardice.com/experimental/magazines.html Hope you find them useful. 2) I haven't yet given up trying to target the different Opera's using the method mentioned at css-discuss. Touble is, I don't have any Opera to confirm with :]. Could someone please just take one more look at the updated Target-a-browser: http://standardice.com/experimental/targetabrowser.html and let me know if there are plenty of errors. (see source for related comments) PS. Sorry Peter, I meant that your #2 looks nice :] DS. /Anton -- What your lacks, your compensates. * The discussion list for http://webstandardsgroup.org/ *
Re: [WSG]WSG Icons
really like to see some comments on this so we actually have a looks nice. /Anton -- What your lacks, your compensates. * The discussion list for http://webstandardsgroup.org/ *
[WSG]Skipper - screen reader for Linux
Don't know if this is common knowledge (didn't find it in the archive) but this screen reader seems very promising (being GPL:ed et al): http://skipper.sourceforge.net/ 'night, /Anton -- What your lacks, your compensates. * The discussion list for http://webstandardsgroup.org/ *
[WSG]Styled indented header
Ran across a good ol' Quark-layouted PDF with a nice header that made me a little jealous of the lack of limits in the desktop world. So I just had to recreate it using CSS :) Here it is: http://standardice.com/experimental/indentedheader.html Comments? /Anton -- What your lacks, your compensates. * The discussion list for http://webstandardsgroup.org/ *
RE: [WSG] padding/margin issue
Gosh, you're fast - I was just about to disconnect my modem ;) Thanx, it was the browser differences I wasn't sure about. /Anton -- What your lacks, your compensates. * The discussion list for http://webstandardsgroup.org/ *
[WSG] padding/margin issue
I read some while ago that the margin-left of the tag is not a margin issue for some browsers but sometimes a _padding_ thingie (maybe for the then?). Can someone confirm this? It might explain some problems I had recently.. cheers, /Anton -- What your lacks, your compensates. * The discussion list for http://webstandardsgroup.org/ *
Re: [WSG]O-matic madness...
Courtesy of Daemon's Browsercam account - actual browser screenshots (not emulations) of your list in: wow, cool.. thx. just a note: IE5/Mac there has weird bug that sometimes shows up the first time you visit the page (i have it here too) but after reloading it looks (at my place) exactly as Mozilla 1.2. /Anton -- What your lacks, your compensates. * The discussion list for http://webstandardsgroup.org/ *
Re: [WSG]O-matic madness...
Opera 7 seems to have a big problem with float boxes inside a floated box. hm, ok.. i'll see what i can do. thanx a lot so far! /Anton -- What your lacks, your compensates. * The discussion list for http://webstandardsgroup.org/ *
Re: [WSG]O-matic madness...
Hi, since I don't have access to more than 2 browsers on my old laptop, could someone please take a look at: http://standardice.com/experimental/nestedlists.html before I submit it to Listamatic2 ? TIA, /Anton -- What your lacks, your compensates. * The discussion list for http://webstandardsgroup.org/ *
IE5/Mac Nested list problem (was: [WSG]list-o-matic-o-rama-o-thingy)
Having played a little more with nested lists now, I get some strange results in IE5/Mac. It occurs when I move the sublist into another toplevel list item, further to the right. Have anyone experienced this? I get a padding-right-like effect of the submenu . E.g., if I move the one list item to the right, it gets narrower (from the right) by the same amount as the distance is to the left side of the browser. I have position: relative; for the toplevel list and position: absolute; with left: 0; for the sublist, both with 100% widths. I can send example code by request, if it's more than a bummer to fix that I just missed. Hm... after throwing one more eye on it, it seems like the behaviour comes from the unability to fully expand into the surrounding toplevel 's width, therefore the subllist gets a fixed width that matches the one it would have without the left: 0; thingie. Adding left: 0; just moves the sublevel (with a now much smaller width) to the very left of the screen. Strange, no? cheers, /Anton -- What your lacks, your compensates. * The discussion list for http://webstandardsgroup.org/ *
[WSG]Target-a-browser
Hi all, I just throwed this page together, happy to get some feedback: http://standardice.com/experimental/targetabrowser.html I lack some browsers and haven't verified the Opera tip someone mentioned on css-discuss yesterday but I guess it's a start anyway. cheers, /Anton -- What your lacks, your compensates. * The discussion list for http://webstandardsgroup.org/ *
Re: [WSG]list-o-matic-o-rama-o-thingy
Wow, have you been listening to the phone conversations between Peter and I? Well, I admit. You're the one with the dark voice, right? ;) You even suggested the same id names - too weird! Well, I just looked at the HTML used in 1.0 so nothing's spooky in here I'm afraid (except my telepatic phone tapping trick above..) Looking forward to your update, I'll try to have a submission ready (although I'm on a Powerbook 3400 with Mac OS 8.6 and have only access to IE5 and Mozilla 1.2.1 which slows me down largely..). cheers, /Anton -- What your lacks, your compensates. * The discussion list for http://webstandardsgroup.org/ *
Re: [WSG]list-o-matic-o-rama-o-thingy
Well... all I can say is that styling lists is VERY popular now: Yeah, but what about nested lists? What about a Listamatic 2.0 with this as a focus? :) Below is a HTML proposal I'm currently playing around with anyway (using instead of #current for increased accessibility): Item one Subitem one Subitem two Subitem three Subitem four Item two Item three Item four (I guess the line breaks after each etc must be removed for better IE support, I just skipped that now for a better visualization.) If you want to see a screen dump of a pilot I made for dn.se using the above code (they wasn't too interested yet though), I put them up at http://standardice.com/dn.html. The page is in Swedish but I guess you get the idea of it. I'm reworking the css at the moment (since it broke in some browsers I didn't have access to) so I'm afraid I can't send you the code yet :/ Oh, the large version pics are in TIFF format and are quite large.. cheers, /Anton -- What your lacks, your compensates. * The discussion list for http://webstandardsgroup.org/ *
Re: [WSG] a new fellow
We are keen to get WSG meetings going in other cities, so it looks like you will have to be our Swedish ambassador, Anton. Hehe.. well, avec plaisir :) If it's world domination you want, I guess wsg-se, wsg-fr etc should be the next logic thing to do to spread the word.. ;) see ya, /Anton -- What your lacks, your compensates. * The discussion list for http://webstandardsgroup.org/ *
