Re: [WSG] Rendering mismatch in IE6 and IE7

2010-03-04 Thread David Hucklesby

On 3/3/10 9:47 PM, Chakravarthy, Srikanth wrote:
[...]


Now is there any way I can identify what CSS properties are not
behaving properly in IE6? Is there any way that I can make the pages
compatible with IE6?



Any reference link or suggestion will be of immense help.



The first thing to realize is that IE 6 has partial support for CSS 1,
while IE 7 introduced some support for CSS 2, particularly the extended
selectors. You may find the Sitepoint CSS reference useful for seeing
which selectors and properties IE 6 actually supports:

  http://reference.sitepoint.com/css

Doubtless you have heard complaints about the colorful bugs with which
this 8+ year old browser is so well endowed. The bugs are quite well
documented, but tend to pop up in unexpected places. As Thierry has
already suggested, asking a specific question about a publicly available
page will likely provide you with better answers than mine.

Cordially,
David
--


***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***



Re: [WSG] Rendering mismatch in IE6 and IE7

2010-03-04 Thread Jon @ The PixelForge
In addition to other advice, you may find that starting with a blank
css sheet and adding in each instruction one by one, and seeing how
each has an effect on the content. Ok, seems obvious, but this will a)
provide you with information on how each instruction is working,
either adversely or by design b) enabling you to learn more how and
why certain bugs appear, speeding up development and debugging in
future projects and c) can provide insight to redundant instructions,
again speeding up future dev and debug time. As much of a PIA as this
may seem, it can be quite interesting, and considering you've already
written the css, it needn't take long.

Admittedly, mostly obvious and I apologise if anything appears
condescending - that is most certainly not my intent. I just think its
worth bearing in mind some good old fashioned detective work can work
wonders. In addition, to add weight to others suggestions, using
browser specific debugging tools in conjunction with this approach has
saved me time (and hair!) in the past.

Regards,

Jon Warner




On Thu, Mar 4, 2010 at 5:42 PM, David Hucklesby huckle...@gmail.com wrote:
 On 3/3/10 9:47 PM, Chakravarthy, Srikanth wrote:
 [...]

 Now is there any way I can identify what CSS properties are not
 behaving properly in IE6? Is there any way that I can make the pages
 compatible with IE6?



 Any reference link or suggestion will be of immense help.


 The first thing to realize is that IE 6 has partial support for CSS 1,
 while IE 7 introduced some support for CSS 2, particularly the extended
 selectors. You may find the Sitepoint CSS reference useful for seeing
 which selectors and properties IE 6 actually supports:

  http://reference.sitepoint.com/css

 Doubtless you have heard complaints about the colorful bugs with which
 this 8+ year old browser is so well endowed. The bugs are quite well
 documented, but tend to pop up in unexpected places. As Thierry has
 already suggested, asking a specific question about a publicly available
 page will likely provide you with better answers than mine.

 Cordially,
 David
 --


 ***
 List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
 Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
 Help: memberh...@webstandardsgroup.org
 ***




***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***



[WSG] Out of Office AutoReply: WSG Digest

2010-03-04 Thread Smith, Lee-Ann
I am currently on leave until Thursday 11 March. Please contact Scott Ashwin if 
you have any urgent mySource or SINA issues (Extension 59169) or email 
det.webad...@act.gov.au

Lee-Ann

Lee-Ann Smith
Online Services Support Officer
Online Systems, InTACT
ACT Dept. Territory  Municipal Services
Phone: 6205 9398 
  
---
This email, and any attachments, may be confidential and also privileged. If 
you are not the intended recipient, please notify the sender and delete all 
copies of this transmission along with any attachments immediately. You should 
not copy or use it for any purpose, nor disclose its contents to any other 
person.
---


***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***


[WSG] Re: WSG Digest

2010-03-04 Thread Ei Sabai Nyo
It should be like this: 

div id=topTop Header.../div
ul
liblah blah blah/li
liblah blah blah/li
/ul
a href=#topback to top/a

And, fyi:
Note that in XHTML 1.0, the name attribute of these elements is
formally deprecated, and will be removed in a subsequent version of
XHTML.
http://www.w3.org/TR/xhtml1/



Anansi Web Development

Web Design and Development | Search Engine Optimisation and Marketing | Social 
Media Integration | Web Application Development

http://www.anansi.com.au/

Web Development Blog
http://eisabainyo.net/weblog



--- On Fri, 5/3/10, wsg@webstandardsgroup.org wsg@webstandardsgroup.org wrote:

From: wsg@webstandardsgroup.org wsg@webstandardsgroup.org
Subject: WSG Digest
To: wsg@webstandardsgroup.org
Received: Friday, 5 March, 2010, 12:55 AM

*
WEB STANDARDS GROUP MAIL LIST DIGEST
*


From: c...@fagandesign.com.au
Date: Thu, 04 Mar 2010 12:33:22 +1100
Subject: IE8 bug?



   Hi all,

   I have run in to what seems to be an IE8 bug - IE8 doesn't respond  
to internal links (as in, same page links) on a demo site I'm working  
onyet IE6 and IE7 do!

eg.
a id=top name=top/a
ul
   liblah blah blah/li
   liblah blah blah/li
/ul
a href=#topback to top/a

   I tried Googling and looking back through old posts from WSG but  
can't find anything

Has anyone come across this issue before? (and better yet, come across  
a fix??)

Regards,

Christian Fagan
Fagan Design
fagandesign.com.au[1]



Links:
--
[1] http://www.fagandesign.com.au



*
From: Micky Hulse mickyhulse.li...@gmail.com
Date: Wed, 3 Mar 2010 17:47:21 -0800
Subject: Re: [WSG] IE8 bug?

 Has anyone come across this issue before? (and better yet, come across a
 fix??)

Not sure if this will help, but I suggest using a div instead of an href:

div id=top.../div

ulliblah blah blah/liliblah blah blah/li/ul

I have not used named anchors in ages.

Hope you get it figured!
M

*
From: John Unsworth john.unswo...@gmail.com
Date: Thu, 4 Mar 2010 12:57:22 +1100
Subject: Re: [WSG] IE8 bug?

Hi Christian,

You will find some info about this on the Sitepoint HTML reference
pages, http://reference.sitepoint.com/html/a/href , read down that
page and there is some information about requiring a href reference in
the anchor link for IE. Also as I understand it you don't really need
id= and name=, use one or the other - they complete the same purpose,
although I'm just reading this information from a book and haven't
checked the specification per se.

Cheers,
John Unsworth

On 4 March 2010 12:33,  c...@fagandesign.com.au wrote:
 Hi all,

 I have run in to what seems to be an IE8 bug - IE8 doesn't respond to
 internal links (as in, same page links) on a demo site I'm working on
yet
 IE6 and IE7 do!

 eg.
 a id=top name=top/a
 ul
    liblah blah blah/li
    liblah blah blah/li
 /ul
 a href=#topback to top/a

 I tried Googling and looking back through old posts from WSG but can't fi
nd
 anything

 Has anyone come across this issue before? (and better yet, come across a
 fix??)

 Regards,

 Christian Fagan
 Fagan Design
 fagandesign.com.au

 ***
 List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
 Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
 Help: memberh...@webstandardsgroup.org
 ***

*
From: Kat k...@t-tec.com.au
Date: Thu, 04 Mar 2010 12:37:02 +1030
Subject: Re: [WSG] Background music on web pages

Lesley Lutomski wrote:
 Thanks to all who have replied.
 
 As far as don't do it goes, you're preaching to the converted here, 
 but I don't seem to be able to get the message through to my clients.
 
 The clients in question are a committee (first problem!), who all say 
 Oh, I know nothing about computers/the internet but at the same time 
 refuse to be guided.  Referring them to usability articles is a 
 non-starter, because they'll just not look at them.  I've tried reducing 
 the arguments to very basic, non-technical issues, but my powers of 
 persuasion are apparently lacking.
 
 Given that I can't afford to turn down the work, I'll take on board the 
 points folk have made here and promise to do the least-awful job on it I 
 can!
 
 Thanks again.
 
 Lesley


Are they business people? Then use business language. Talk about their 
marketing/advertising/ and the budget and the daily work, 24/7, at 
achieving their brand/image that goes on by everyone at the 
organisation. That if someone has a bad experience, it has a bigger then 
expected negative impact: they will tell 20 people. That background 
music is an instant bad 

RE: [WSG] Rendering mismatch in IE6 and IE7

2010-03-04 Thread Chakravarthy, Srikanth
Hi,

Thanks for all the inputs.

I will not be able to provide a link to the page.
I will definitely take all your advice and try sorting out the properties that 
do not work with IE6.

Thanks
Srikanth

-Original Message-
From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org] On 
Behalf Of Jon @ The PixelForge
Sent: Friday, March 05, 2010 3:40 AM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] Rendering mismatch in IE6 and IE7

In addition to other advice, you may find that starting with a blank
css sheet and adding in each instruction one by one, and seeing how
each has an effect on the content. Ok, seems obvious, but this will a)
provide you with information on how each instruction is working,
either adversely or by design b) enabling you to learn more how and
why certain bugs appear, speeding up development and debugging in
future projects and c) can provide insight to redundant instructions,
again speeding up future dev and debug time. As much of a PIA as this
may seem, it can be quite interesting, and considering you've already
written the css, it needn't take long.

Admittedly, mostly obvious and I apologise if anything appears
condescending - that is most certainly not my intent. I just think its
worth bearing in mind some good old fashioned detective work can work
wonders. In addition, to add weight to others suggestions, using
browser specific debugging tools in conjunction with this approach has
saved me time (and hair!) in the past.

Regards,

Jon Warner




On Thu, Mar 4, 2010 at 5:42 PM, David Hucklesby huckle...@gmail.com wrote:
 On 3/3/10 9:47 PM, Chakravarthy, Srikanth wrote:
 [...]

 Now is there any way I can identify what CSS properties are not
 behaving properly in IE6? Is there any way that I can make the pages
 compatible with IE6?



 Any reference link or suggestion will be of immense help.


 The first thing to realize is that IE 6 has partial support for CSS 1,
 while IE 7 introduced some support for CSS 2, particularly the extended
 selectors. You may find the Sitepoint CSS reference useful for seeing
 which selectors and properties IE 6 actually supports:

  http://reference.sitepoint.com/css

 Doubtless you have heard complaints about the colorful bugs with which
 this 8+ year old browser is so well endowed. The bugs are quite well
 documented, but tend to pop up in unexpected places. As Thierry has
 already suggested, asking a specific question about a publicly available
 page will likely provide you with better answers than mine.

 Cordially,
 David
 --


 ***
 List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
 Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
 Help: memberh...@webstandardsgroup.org
 ***




***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***



Misys is the trade name for Misys plc (registered in England and Wales). 
Registration Number: 01360027. Registered office: One Kingdom Street, London W2 
6BL, United Kingdom. For a list of Misys group operating companies please go to 
http://www.misys.com/corp/About_Us/misys_operating_companies.html. This email 
and any attachments have been scanned for known viruses using multiple 
scanners. This email message is intended for the named recipient only. It may 
be privileged and/or confidential. If you are not the named recipient of this 
email please notify us immediately and do not copy it or use it for any 
purpose, nor disclose its contents to any other person. This email does not 
constitute the commencement of legal relations between you and Misys plc. 
Please refer to the executed contract between you and the relevant member of 
the Misys group for the identity of the contracting party with which you are 
dealing. 


***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***