Dave wrote:
>> Of course it also puts its credibility at risk if it publishes a 
>> Recommendation
>> for something that UAs cannot implement for legal reasons.
> 
> Do you think the EOT submission has legal problems?

I have no idea.  I'm not a lawyer.  But I'm given to understand that @font-face 
with a DRM-less format might.  Things are murky.

> My understanding of CSS2 and MSIE is that everyone else did not
> reverse-engineer its quirks

Your understanding is somewhat lacking. There are all sorts of things in CSS2.1 
that were written by reverse-engineering the MSIE behavior.  Sizing of 
absolutely positioned replaced elements comes to mind.  The proposed models for 
table layout (which CSS2 doesn't really so much define) are somewhat based on 
reverse-engineering (though not completely).  If there were no attempt to be 
compatible with IE in various aspects of layout, the specification would be a 
little simpler and more logical in various areas.

>> You mean browsers?  They're not _that_ easily upgraded.  See the IE6 usage
>> figures.  And content is nearly impossibly to upgrade on any sort of large 
>> scale.
> 
> I meant very generally that software is more upgradeable than
> hardware

I agree, but hardware is _much_ more upgradeable than content.  Hardware is 
routinely upgraded on a 3-year cycle.  For comparison, the BBC News web site 
just had its first redesign in at least 5 years.  The W3C website front page 
hasn't really been "upgraded" in a very long time.

You could argue that they aren't changing because there is no need to change, 
but the fact is that sheer volume of content makes it impossible to upgrade on 
a 
schedule.

And the danger with premature implementation of proposed standards is that 
content comes to depend on them.  And then the implementor can't change the UA 
even if it wants to.

> I guess I'm saying "There's now three web browsers that do so, let's
> not get left behind"...

Which is reasonable.  Again, I'm not saying that @font-face isn't something 
desirable.  It is.  I'm saying that unlike other parts of CSS, even once the 
technical issues are resolved there is a nasty legal issue lurking that would 
need to be at least carefully thought about.  Probably in consultation with 
some 
competent lawyers and possible with the CSS Working Group.

-Boris
_______________________________________________
dev-tech-layout mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-layout

Reply via email to