On Jul 2, 2014, at 4:01 AM, Ryosuke Niwa rn...@apple.com wrote:
On May 15, 2014, at 10:01 AM, Elliott Sprehn espr...@chromium.org wrote:
On Tue, May 13, 2014 at 11:21 AM, Ian Hickson i...@hixie.ch wrote:
I would feel more comfortable putting things on SVG, MathML, and HTML
explicitly.
On 14/07/2014 09:43, Dirk Schulze wrote:
However, I would like to know what use cases and problems Dirk is trying to
solve by moving these attributes from HTMLElement to Element. Dirk, could you
elaborate on that?
If you add contentEditable to an HMTL element and an SVG element is an
Le 13/05/2014 18:21, Ian Hickson a écrit :
On Tue, 13 May 2014, Dirk Schulze wrote:
contentEditable can be fairly useful in SVG as well. It partly works for
inline SVG content in web browsers today.
The question is, should SVGElement add support for
contentEditable/isContentEditable and add it
On May 15, 2014, at 10:01 AM, Elliott Sprehn espr...@chromium.org wrote:
On Tue, May 13, 2014 at 11:21 AM, Ian Hickson i...@hixie.ch wrote:
I would feel more comfortable putting things on SVG, MathML, and HTML
explicitly.
I don't think we want contenteditable in SVG or MathML. Almost all
On Tue, May 13, 2014 at 11:21 AM, Ian Hickson i...@hixie.ch wrote:
On Tue, 13 May 2014, Dirk Schulze wrote:
contentEditable can be fairly useful in SVG as well. It partly works for
inline SVG content in web browsers today.
The question is, should SVGElement add support for
On Tue, May 13, 2014 at 11:26 AM, Dirk Schulze dschu...@adobe.com wrote:
contentEditable can be fairly useful in SVG as well. It partly works for
inline SVG content in web browsers today.
The question is, should SVGElement add support for
contentEditable/isContentEditable and add it to its
On 13/05/2014 10:26, Dirk Schulze wrote:
Hi,
contentEditable can be fairly useful in SVG as well. It partly works
for inline SVG content in web browsers today.
The question is, should SVGElement add support for
contentEditable/isContentEditable and add it to its interface? Or
should both
On Tue, 13 May 2014, Dirk Schulze wrote:
contentEditable can be fairly useful in SVG as well. It partly works for
inline SVG content in web browsers today.
The question is, should SVGElement add support for
contentEditable/isContentEditable and add it to its interface? Or should
both
