Search Type: Posts; User: xor
Search: Search took 0.03 seconds.
6 Jul 2014 5:37 AM
sseema, I doubt it is related to Ext.ux.TinyMCE, but rather to TimyMCE itself. So you'd better to ask this question at their support forums.
24 Oct 2012 7:48 AM
Guys, I finally published the component at the GitHub. Don't know what prevented me to do it before, so don't ask. :)
N.B. The code there also contains Ext.ux.TinyMCE version for ExtJS 4. Somewhat...
25 Apr 2012 10:57 PM
Extension does not require. But if you'd choose jQuery-base TinyMCE version, then it would be of course necessary.
13 Sep 2011 10:17 PM
Can you make a test page reproducing this bug?
8 Sep 2011 10:58 PM
Actually it is not a browser default font but rather editor's default font, which is specified in the editor's default CSS file. You can find it somewhere in the editor's directory. Currently I don't...
25 Aug 2011 6:35 AM
Here you are: version 0.8.2.
23 Aug 2011 1:45 AM
Please try how does it work in plain TinyMCE. I doubt that my component alters this behavior.
17 Aug 2011 7:33 AM
Guys, sorry for being soo slooow, but I finally made an update. You can download it from our site:
Fixed problems, reported by you in this thread....
17 Aug 2011 3:30 AM
I agree with you about the semanitcs of the form field. And this is definitely my bug, that I fire event with inner editor. But you also break the semantics, when you wire "keypress" and other...
16 Mar 2011 12:07 PM
It definitely will work with Ext 4. But, I afraid, only after we'll start migrating our application to Ext 4. We didn't try yet.
5 Jul 2010 2:32 AM
Try using TinyMCE variant that is not bound to jQuery.
1 Jul 2010 11:29 PM
Try version 0.8.5 - http://blogs.byte-force.com/media/p/40520.aspx
It should fix the bug with alert popping under the modality shadow.
As for scissors - this is not "delete", this is...
1 Jul 2010 11:15 PM
Styles is populated with CSS classes that TinyMCE finds in CSS file that you specify. If you don't give it such file, or the file doesn't contain standalone classes (i.e. simpliest...
29 Jun 2010 12:00 AM
I afraid, there is no backward compatibility with older Ext versions. So maybe someone still have Ext.ux.TinyMCE version compatible with Ext 2.2.
28 Jun 2010 7:13 AM
Ext.ux.TinyMCE doesn't depend on ManagedIFrame any more. Thanks to community. So you can have any version of ManagedIFrame, my control shouldn't notice it.
24 Jun 2010 4:15 AM
So, it is working? Great. I'll slo-o-owly prepare the release then.
23 Jun 2010 12:28 AM
Please also try this new version. Does it correctly perform lazy definition of WindowManager and ControlManager classes in your case?
23 Jun 2010 12:10 AM
@dumbledore, please try the version with windowGroup support. Just specify it in "manager" configuration parameter for the editor.
22 Jun 2010 10:58 PM
Sorry, can't say anything valuable on this issue. Looks like I never saw such behavior in my applications. Maybe you can build up a test case that shows this problem on base on my test...
22 Jun 2010 5:01 AM
Toon, get to component's instance using Ext.getCmp() method. Then go to editor using "ed" property and use its API to do what you want. Editor's API is described in details at TinyMCE site.
2 Jun 2010 4:00 AM
Can you make a test case on base of my test.* files?
1 Jun 2010 1:07 AM
What if it will be possbile to specify WindowGroup for the instance of Ext.ux.TinyMCE to use?
24 May 2010 11:11 PM
Dumbledore, just a though: maybe Editor by itself uses special window group that we can get and pass to Ext.ux.TinyMCE instance?
19 May 2010 2:07 AM
Yes, asagala, windowGroup appears to be a bad idea. As I understand, it now works only if you put the component in Editor. And in all other cases there are problems with popups.
13 May 2010 2:32 AM
sirioz10, nice hack! :) But I don't think we should include in into official version. After all, this is a hack. So if one suffers from this problem, he can go and apply your workaround.
Results 1 to 25 of 120