|
|
Posted by Gιrard Talbot on 02/06/06 21:10
Barbara de Zoete wrote :
> On Mon, 06 Feb 2006 17:43:13 +0100, GΓ©rard Talbot
> <newsblahgroup@gtalbot.org> wrote:
>
>> Barbara de Zoete wrote :
>>> <abbr>Abbr.</abbr>.
>
>>> <html lang="en">
>>> <head>
>>> <style type="text/css">
>>> abbr[title] {
>>> border-bottom:1px dotted maroon;
>>> cursor:help; }
>>> </style>
>>> </head>
>>> <body>
>>> <p>The title attribute could be of good value if a web author uses
>>> an <abbr title="Abbreviation">abbr</abbr>.
>>
>> For the first occurence, it's possible to do it like this:
>>
>> <dfn><abbr title="Abbreviation">abbr</abbr> (Abbreviation)</dfn>
>
> This is a new element for me, this 'instance definition'. Saw it
> appearing in a few posts recently. So I looked it up and I like it.
> Haven't used it anywhere myself, but might start to do that.
WHAT's Web Applications 1.0 gives examples and info on this issue:
http://www.whatwg.org/specs/web-apps/current-work/#the-abbr
http://www.whatwg.org/specs/web-apps/current-work/#the-dfn
>
>>> <p>Note though that the selector abbr[title] doesn't work in IE
>>> (what else is new).</p>
>>
>> I really must say /want to say that
>> - IE 7 beta 2 supports attribute selector and
>> - IE 7 beta 2 also supports <abbr> like it should.
>
> Really? That is good news.
I couldn't resist replying to your "what else is new"... :)
At least somewhere in the years to come the
> majority of people might switch to a browser that supports what is
> todays standard ;-)
You're absolutely right. IE7 beta 2 fixed only 11 issues overall and
many hundreds of bugs, feature requests, support+implementation requests
have been ignored so far... and that is notwithstanding many regression
bugs found so far. As one said:
"maybe we'll get the CSS 2.1 support we desire in IE8 sometime in 2012,
of course by then we'll all want CSS4 support."
http://blogs.msdn.com/ie/archive/2006/02/02/523679.aspx#524110
This is what I wrote at Molly's website on july 29th 2005
http://www.molly.com/2005/07/28/thats-why-its-called-beta/#comment-11550
"
Even if Microsoft would fix half of the documented, reported bugs and
implement just half of the missing, incomplete support for CSS2, DOM 2,
and other expressed/formulated specific requests in the final release of
MSIE 7, there would be major problems for web developers.
1- People do not automatically upgrade to the latest available browser
release. Adoption/migration of more recent browser release versions is a
slow process and takes years. Studies have shown that a majority of
people usually go ahead with a browser upgrade along/at the same time
with an operating system upgrade. So one should expect to see MSIE 6 to
represent a large chunk of the browser market for the next 5 years or so.
2- Many windows users will not be able to upgrade to MSIE 7 anyways
since MSIE 7 will be possible only for XP users and Windows 2003 users.
A considerable minority (20% - 30%) of the windows market will not be
using MSIE 7 anyway during the next few years.
So, regarding web standards support and compliance in browser usage,
developers will have to deal with an overall fragmented browser picture
in the years to come. That's at best.
Now the only remaining question is how well, good, complete, how much
will the MSIE 7 final release fix the utterly explained, described,
documented CSS/DOM bugs, unsupported DOM 2 attributes, methods,
unsupported CSS 2.1 properties? This beta 1 release is sending the
message; it suggests me that we should not expect more than a 50% effort
from Microsoft.
So, speaking of patience means in my mind that things will be fixed
completely and for good with MSIE 8 ... around 2012.
"
http://www.molly.com/2005/07/28/thats-why-its-called-beta/#comment-11550
GΓ©rard
--
remove blah to email me
Navigation:
[Reply to this message]
|