Any chance we will be seeing contenteditable on top of polymer elements

446 views
Skip to first unread message

abhinav gupta

unread,
Aug 28, 2014, 11:46:39 AM8/28/14
to polym...@googlegroups.com
"There have been some rumblings lately from some Chromium contributors (Levi Weintraub, Julie Parent, and Jelte Liebrand) that they want to redo ContentEditable on top of Polymer Elements and Shadow DOM."
Is there any chance that we will be getting contenteditable ported to Polymer Elements so one can create wysiwyg editor easily on top of polymer elements? I cant find a wysiwyg editor implemented as a polymer element yet.

Sébastien Cevey

unread,
Aug 28, 2014, 12:05:24 PM8/28/14
to abhinav gupta, polym...@googlegroups.com
Hey,

FYI I mocked up a quick Polymer element for our Scribe rich-text editor [1] during a recent session on Web Components at the Google Campus.


The code is very rough but it shows what's possible. Sorry no docs or anything at this stage, but the demo should work.

Feedback welcome!



On 28 August 2014 16:46, abhinav gupta <abhin...@gmail.com> wrote:
"There have been some rumblings lately from some Chromium contributors (Levi Weintraub, Julie Parent, and Jelte Liebrand) that they want to redo ContentEditable on top of Polymer Elements and Shadow DOM."
Is there any chance that we will be getting contenteditable ported to Polymer Elements so one can create wysiwyg editor easily on top of polymer elements? I cant find a wysiwyg editor implemented as a polymer element yet.

Follow Polymer on Google+: plus.google.com/107187849809354688692
---
You received this message because you are subscribed to the Google Groups "Polymer" group.
To unsubscribe from this group and stop receiving emails from it, send an email to polymer-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/4bfcbbb6-45ad-4b38-9d58-114779c37967%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
Sébastien Cevey
Software Developer


Visit theguardian.com. On your mobile and tablet, download the Guardian iPhone and Android apps theguardian.com/guardianapp and our tablet editions theguardian.com/editions.  Save up to 57% by subscribing to the Guardian and Observer - choose the papers you want and get full digital access.  Visit subscribe.theguardian.com

This e-mail and all attachments are confidential and may also be privileged. If you are not the named recipient, please notify the sender and delete the e-mail and all attachments immediately. Do not disclose the contents to another person. You may not use the information for any purpose, or store, or copy, it in any way.  Guardian News & Media Limited is not liable for any computer viruses or other material transmitted with or as part of this e-mail. You should employ virus checking software.
 
Guardian News & Media Limited is a member of Guardian Media Group plc. Registered Office: PO Box 68164, Kings Place, 90 York Way, London, N1P 2AP.  Registered in England Number 908396


abhinav gupta

unread,
Aug 28, 2014, 12:17:36 PM8/28/14
to polym...@googlegroups.com, abhin...@gmail.com
This is great stuff. I had looked into scribe before and was looking into making component out of it myself. This will help me a lot. Thanks!

abhinav gupta

unread,
Aug 28, 2014, 12:48:26 PM8/28/14
to polym...@googlegroups.com, abhin...@gmail.com
Hey
I was checking out the code. Is there any particular reason you are not using "domReady", instead using "ready" with the hack "// FIXME: hacky delay to fix init order...". Because I tried with domReady without hackyDelay function and it is working. This is my first time using polymer, so forgive me if I am totally wrong.


On Thursday, August 28, 2014 9:35:24 PM UTC+5:30, Sébastien Cevey wrote:
Reply all
Reply to author
Forward
0 new messages