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