Priority: Normal
Current State: Waiting for Release
Released In: 2.1.9
Target Release: patch
This is a tough one. There are lots of wiki apps out there depending on plugin params being embedded into the class attribute. As per xhml there's no other place where to put it. Only html5 allows us to
have custom
data-...
attributes in the DOM node. However the standard foswiki skin still runs on XHTML 1.0 Transitional.
The recommended way to specify jQuery plugin parameters in a declarative way is by custom
data-...
attributes, thus removing the need for a separate jquery.metadata plugin, which btw isn't maintained anymore.
--
MichaelDaum - 29 May 2013
Is this ready to go to Waiting for Release in 1.2?
--
GeorgeClark - 29 May 2014
The deprecation can start but we can not eliminate or even reduce the use of jquery.metadata more in the scope of 1.2.0 as this would create a lot of incompatibility. This work has to be continued after 1.2.0 was released.
--
MichaelDaum - 29 May 2014
Push to 2.1
--
GeorgeClark - 06 Jul 2015
Let's proceed as follows:
- add support for html5 data in addition to the old metadata approach
- deprecate metadata by issuing a warning if still used the javascript console
- remove/disable metadata
(1) can happen asap, i.e in the next patch release; there is zero risk here (2.1.5 as by now)
(2) can be added in the next minor release (2.2.0 as by now)
(3) finally remove metadata in the next major release (3.0 or so)
--
MichaelDaum - 06 Dec 2017
ui::autocomplete still depends on metadata.
--
MichaelDaum - 08 Nov 2024