-
Notifications
You must be signed in to change notification settings - Fork 369
Inline editors do not work #41
Comments
I came across this same issue when trying to find a work-around for #38. I ended up creating a new version of the directive, specifically for inline editors. It's in my own fork of this repo: https://github.com/gunnarlium/ui-tinymce/blob/inline-editor-version/src/tinymce-inline.js. It's really just a quick and dirty effort to get something that solves my immediate problem, but if there's any interest, I'd be happy to collaborate to create something that can me merged into the main repo. |
The problem is with 51 line. Editor is saved after keyup event. This update cursor position. I dont know how to property fix but i know when i change code to this:
It work quite well. |
This should be fixed via cafdfa7 |
Hello! |
What version of the library are you using? Can you please post a plunker showing your example with the issue? |
Want to say that we have the same trouble only in Firefox. |
What version of the library are you using? Can you please post a plunker showing your example with the issue? |
I have the same problem. angular-ui-tinymce doesn't work on textareas. Text shows as raw. Cant edit anything. But the menu does show up: on osx with: Safari versions: |
Can you please post a plunker demonstrating the issue so we can look into fixing it? |
http://plnkr.co/edit/10H6rbwP3xycbb493F9B?p=preview Plunkr with newest versions: Angular Ui Tinymce - 0.0.11 As you see, the textarea doesn't parse the text and you cant edit. |
Any news on the problems? Otherwise inline seems broken in all browsers with the current versions. |
Sorry for the delay. I am going to look into it this week. I am going to re-open the issue for now. |
Changing the textarea to a div in your example, everything works fine.
Is there any reason you want to use a textarea instead of a div in this situation? You will see their example also does not use a textarea. I think you will find this issue has more to do with the TinyMCE library itself, rather than the angular wrapper. |
I'm new to tinymce and this module but got inline to work within minutes. Textarea should never work as inline, that is "the wrong way to do things" as inline should keep the original tag (textarea) and textarea doesn't support formating. Here's a screenshot of successful integration in 2sxc from yesterday when I just got started ...so I would close this issue |
Hi ! |
My bad, I was using on the same element "ng-bind-html". |
Sorry, we're still seeing it fail. The $scope var is not updated, even though it does initially bind from the ng-model var. Try changing the content in the first editor tab. The p below is bound to the same scope var, and the button shows the scope var. Neither of these shows the right value after changing the bound tinymce div. |
Same issue here, the caret keeps going to the beginning of the line. Tried both Div and Text area, still the same :( |
When TinyMCE is configured to appear in "inline" mode, via the
inline: true
configuration option, then text entry does not work properly. With a textarea element, the text disappears, whereas with divs, the caret is repeatedly moved to the beginning of the content, resulting a kind of backwards-writing effect. See this plunkr for a demonstration (happens in Chrome and Firefox).http://plnkr.co/edit/w86QRKvuTAJKd9TZvR9a?p=preview
The text was updated successfully, but these errors were encountered: