On Thu, 20 Nov 2008, Michael A. Puls II wrote: > > The spec currently says that Opera, Firefox and Safari can use the > classid attribute to load the plugin if they want. This might be done by > mapping a classid to a plugin handler. They just need to fall back if > that fails, instead of then trying type and data. > > The danger of mapping classid for non-activex browsers is that sometimes > an <object> that uses classid="" might be meant for an activeX plugin > that uses a different API than the NPAPI version of the plugin. This > where vendors would have to be careful before deciding what classids to > support. > > If that's not the handling intended by the spec and classid is meant to > be IE-only, the spec should be clarified. classid isn't a valid > attribute, so maybe that doesn't matter.
What you describe is what I intended. There's a commented list of IDs that maybe they should support (based on what they do support) but I don't know whether to make it formal or not. So far I've opted to not make it formal. I think it might depend on a platform-by-platform basis. -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
