Re:X-editable: In-place editing with Twitter Bootstrap, jQue...
by masklinn on Sunday November 25, 2012 @10:07AM
(#4828275)
Aloha is an RTE, I'm not talking about RTEs in my comment I'm talking about bare, basic fields. Such as the one I'm typing/editing this comment in.
[ Parent
| on HN ]
Re:X-editable: In-place editing with Twitter Bootstrap, jQue...
by laktek on Sunday November 25, 2012 @11:03AM
(#4828394)
Aloha is not a traditional WYISWYG editor contained in a textarea. You can apply it to any HTML element in a page, which would turn them in to editables (check this example of math editing - http://wysiwhat.github.com/Aloha-Editor/cnx.html)
Re:X-editable: In-place editing with Twitter Bootstrap, jQue...
by scribu on Sunday November 25, 2012 @11:59AM
(#4828540)
Doesn't work in Firefox.
OT: Am I the only one annoyed by this "viewed best in Chrome" trend? Reminds me of those old "Best in IE" badges.
Re:X-editable: In-place editing with Twitter Bootstrap, jQue...
by Surio on Sunday November 25, 2012 @12:27PM
(#4828620)
No, you are not alone. And I am sad to miffed at lack of support for Opera too.
There was a jquery fundamentals website that had the same problem. To compound matters, Chrome font rendering is godawfully bad on my machine.
Re:X-editable: In-place editing with Twitter Bootstrap, jQue...
by fredsted on Sunday November 25, 2012 @01:45PM
(#4828840)
Works fine in Firefox 17, try updating your browser.
Re:X-editable: In-place editing with Twitter Bootstrap, jQue...
by scribu on Sunday November 25, 2012 @03:12PM
(#4829122)
I was running Firefox 16.0.2. I updated to Firefox 17 and it still doesn't work; I can't edit or change anything.
Re:X-editable: In-place editing with Twitter Bootstrap, jQue...
by Surio on Sunday November 25, 2012 @09:16PM
(#4830081)
I am also beginning to find this browser update treadmill very tedious.
Re:X-editable: In-place editing with Twitter Bootstrap, jQue...
by masklinn on Sunday November 25, 2012 @12:01PM
(#4828548)
> Aloha is not a traditional WYISWYG editor contained in a textarea.
Did you miss the part where I said I wasn't talking about RTE?
I don't care that it's implemented using something which was introduced to build RTEs in the first place and has been used for exactly that for the past 12 years or so (which does happen to make contenteditable-based RTEs traditional, as are designMode-based ones, despite your apparent assertion to the contrary), my original comment is not about rich text edition.