[uf-discuss] Include-pattern issues
karnsj at cse.ohio-state.edu
Sun Feb 4 22:04:02 PST 2007
> -----Original Message-----
> From: microformats-discuss-bounces at microformats.org
> [mailto:microformats-discuss-bounces at microformats.org] On
> Behalf Of Breton Slivka
> Sent: Monday, February 05, 2007 12:51 AM
> To: Microformats Discuss
> Subject: Re: [uf-discuss] Include-pattern issues
> If I remember correctly, these issues can be dealt with by
> using an <a> element instead of an object element. This is
> endorsed in the spec for the pattern, I believe.
> On 05/02/2007, at 4:00 PM, Jason Karns wrote:
> > I have two issues with the include-pattern, though they are
> less with
> > the pattern itself and more with simply implementing it.
> > 1) When using IE (6 and 7) there are many styling issues
> involved with
> > hiding the object element. Simply display:none is not sufficient.
> > 2) Many accessibility 'validators' will flag empty <object>
> > as errors if no fallback text is supplied.
> > Should these issues be listed on the wiki under include-pattern
> > issues, or on a page as special notes about authoring with the
> > include-pattern?
> > Jason Karns
> > ~~~~~~~~~~~
> > The Ohio State University [www.osu.edu] Computer Science &
> > [www.cse.osu.edu]
> > _______________________________________________
> > microformats-discuss mailing list
> > microformats-discuss at microformats.org
> > http://microformats.org/mailman/listinfo/microformats-discuss
> microformats-discuss mailing list
> microformats-discuss at microformats.org
That's correct. I meant for these issues to be more like notices when
deciding between <object> and <a>. When I first started using the include
pattern, only <object> was supported. Luckily, Safari caused enough trouble
that <a> was included as an option. I meant to only add these issues as
further reasons for using <a>.
More information about the microformats-discuss