There have been several postings recently dealing with bugs in
Internet Explorer. Can anyone point me to a review of these bugs and
how to work around them?

Regards, Alex

Alex Bell wrote:[color=blue]
> There have been several postings recently dealing with bugs in
> Internet Explorer. Can anyone point me to a review of these bugs and
> how to work around them?[/color]

http://www.google.com/search?q=msie%...r%20css%20bugs

(hint: you could have done this yourself, and not waited for an answer)

--
Brian
follow the directions in my address to email me

On Wed, 01 Oct 2003 01:46:00 GMT, Brian
<usenet1@mangymutt.com.invalid-remove-this-part> wrote:
[color=blue]
>Alex Bell wrote:[color=green]
>> There have been several postings recently dealing with bugs in
>> Internet Explorer. Can anyone point me to a review of these bugs and
>> how to work around them?[/color]
>
>http://www.google.com/search?q=msie%...r%20css%20bugs
>
>(hint: you could have done this yourself, and not waited for an answer)[/color]

In Alex's defence, the above search returns 5,660 results. I think
s/he was looking for someone who could recommend a specific
list/review, rather than having to trudge through so many results,
which - I'm sure you'll agree - may not be all that reliable or
complete.
Many other posts have garnered recommendations for certain tutorials
when requested, rather than receive advice to go
http://www.google.com/search?q=css%20tutorial
which gives 345,000 results, btw.
Sorry. That's just my two cents....

On Wed, 01 Oct 2003 07:14:48 GMT, Jane Withnolastname
<JaneWithnolastnameNOSPAM@yahoo.com> wrote:
[color=blue]
>On Wed, 01 Oct 2003 01:46:00 GMT, Brian
><usenet1@mangymutt.com.invalid-remove-this-part> wrote:
>[color=green]
>>Alex Bell wrote:[color=darkred]
>>> There have been several postings recently dealing with bugs in
>>> Internet Explorer. Can anyone point me to a review of these bugs and
>>> how to work around them?[/color]
>>
>>http://www.google.com/search?q=msie%...r%20css%20bugs
>>
>>(hint: you could have done this yourself, and not waited for an answer)[/color]
>
>In Alex's defence, the above search returns 5,660 results. I think
>s/he was looking for someone who could recommend a specific
>list/review, rather than having to trudge through so many results,
>which - I'm sure you'll agree - may not be all that reliable or
>complete.
>Many other posts have garnered recommendations for certain tutorials
>when requested, rather than receive advice to go
>http://www.google.com/search?q=css%20tutorial
>which gives 345,000 results, btw.
>Sorry. That's just my two cents....[/color]

Thanks, Jane. That was exactly my reasoning, and is why I asked for a
definitive guide.

Regards, Alex

Jane Withnolastname wrote:[color=blue]
> On Wed, 01 Oct 2003 01:46:00 GMT, Brian wrote:
>[color=green]
>>Alex Bell wrote:
>>[color=darkred]
>>> bugs in Internet Explorer. Can anyone point me to a
>>> review of these bugs and how to work around them?[/color]
>>
>> http://www.google.com/search?q=msie%...r%20css%20bugs
>>
>> (hint: you could have done this yourself, and not waited for an answer)[/color]
>
> In Alex's defence, the above search returns 5,660 results.[/color]

Google page ranks counts, among other things, inbound links. It's a
democracy -- with limitations, to be sure -- where every inbound link
counts and puts you higher in the rankings. With that in mind, I went
back to the search results to see how it did.

first link, dbaron.org. It's a test of MSIE against the w3c css
suite. Perhaps only useful if you know the suite, but at the bottom
is a list of unsupported features. Good resource.

second link, a list apart. A bug in scrolling in MSIE6, with a
javascript solution. Ok resource.

third link, dev.apple.com. A nice list of bugs in IE/Mac, along with
a useful css hack to hide css from it. Looks excellent to me.

fourth link, w3c.org. I cannot get it to load at the moment. We'll
call that a dud.

fifth link, css.nu. Paydirt. A long list of bugs, with workarounds
provided where they are known. And this domain also hosts the ciwas faq.

All in all, I think Google did pretty well.
[color=blue]
> s/he was looking for someone who could recommend a specific
> list/review, rather than having to trudge through so many results,
> which - I'm sure you'll agree - may not be all that reliable or
> complete.[/color]

The results on the first page look pretty good to me. It's a question
of efficiency. When I saw the op, my first reaction was to try to
answer the quesion. I could have searched through my long list of
bookmarks for IE specific sites, but that might not have turned much
up. So I went to Google instead, to see what it turned up. And it
turned up a lot. That didn't require specialized knowledge on my part.

For the OP, (s)he posted a query, waited for a response, and after
some time, got an answer (s)he could have had immediately. I dunno, I
thought (s)he might want to know how to get it more quickly next time.

--
Brian
follow the directions in my address to email me