W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > February 2010

[Bug 8828] definition of "plugin"

From: <bugzilla@wiggum.w3.org>
Date: Sun, 14 Feb 2010 09:36:03 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1NgatX-0004dI-Qm@wiggum.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8828


Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED




--- Comment #5 from Ian 'Hixie' Hickson <ian@hixie.ch>  2010-02-14 09:36:03 ---
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are
satisfied with this response, please change the state of this bug to CLOSED. If
you have additional information and would like the editor to reconsider, please
reopen this bug. If you would like to escalate the issue to the full HTML
Working Group, please add the TrackerRequest keyword to this bug, and suggest
title and text for the tracker issue; or you may create a tracker issue
yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Partially Accepted
Change Description: see diff given below
Rationale: I've attempted to make the definition more self-consistent.

It's possible for a plugin to support JPG types, yes. More common is for
browsers to natively support SVG or PDF yet have that support fall into the
"plugin" definition. Really the only effect is whether <embed> can display the
content or not.


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Sunday, 14 February 2010 09:36:05 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:11 UTC