Technology requirements in browsers

Benton, Kevin kevin.benton at amd.com
Thu Mar 2 00:21:39 UTC 2006


> Benton, Kevin wrote:
> > I suggest we have technology requirements rather than specific
browser
> > versions.  That way, we don't need to add new browsers when they
begin
> > to meet the standards.
> Good idea.
> 
> > So, I would rather see things like:
> >
> > XHTML
> > CSS 2
> > ECMAScript 1
> >
> We might outline the policy change broadly (f.e. we'll allow the use
of
> technologies supported by popular browsers or available to most web
> users), but given that we're opening up new possibilities and don't
yet
> have lots of implementation experience, I suggest we take a wait and
see
> approach to specifying exactly which technologies we allow and give
our
> developers some room to experiment and present us with some
> implmentations.

I agree.  Note that my reasoning behind throwing out the list above was
to simply pass along an example.  In no way was it intended to be a real
suggestion of technology requirements.  I'd need to do more research
before making any kind of suggestion there.

Having said that, when CSS3 becomes widely adopted, it'll make preparing
text for printing far easier than it is now.  I'm already using CSS2
with HTML(4) to do literary artwork, but CSS3 would be a lot better.  I
think CSS2 seems like a very reasonable requirement because it'll make
handling dynamic fields a bunch easier. :)

---
Kevin Benton
Perl/Bugzilla Developer/Administrator, Perforce SCM Administrator
Personal Computing Systems Group
Advanced Micro Devices
 
The opinions stated in this communication do not necessarily reflect the
view of Advanced Micro Devices and have not been reviewed by management.
This communication may contain sensitive and/or confidential and/or
proprietary information.  Distribution of such information is strictly
prohibited without prior consent of Advanced Micro Devices.  This
communication is for the intended recipient(s) only.  If you have
received this communication in error, please notify the sender, then
destroy any remaining copies of this communication.





More information about the developers mailing list