Hi,
When I run the attached form with the latest Orbeon release (orbeon-4.3.0.1.201308150213-CE), 2 TinyMCE editors appear, but they are not positioned at the location I’d expect. For each title “Text area x”, a TinyMCE editor should be displayed, but they both appear at the end.
This only happens with Chrome (it behaves correctly in Firefox and Internet Explorer), and only if the page is an XSL stylesheet (when I make it a static XHTML page, it works correctly).
How to reproduce: - Click "b" in the Section-dropdown - Select the Expand-checkbox Observed behavior: - Two text areas appear after "Text Area 1 - Text area 2" Expected behavior: - The first Text Area should appear between the "Text area 1" and "Text area 2" Notes: - This is only a problem in Chrome. It works correctly in Firefox and Internet Explorer - It works in Chrome too, if I remove the xsl:version attribute from the root - It works in Chrome too, if the initial value of "section" is "b" - It works in Chrome too, if I remove the empty div-element at the bottom Environment: - Google Chrome Version 30.0.1599.101 m: NOK - Firefox 24.0: OK - Internet Explorer 10: OK
Thanks in advance,
Tars Joris Development Manager Inventive Designers Inventive Designers' Email Disclaimer: http://www.inventivedesigners.com/email-disclaimer -- You received this message because you are subscribed to the Google Groups "Orbeon Forms" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. To post to this group, send email to [hidden email]. tiny-mce-out-of-place.xsl (3K) Download Attachment |
Administrator
|
Hi Tars,
Good news: while I can reproduce this with Chrome 30, it is working with Chrome 32 (the current version in the Dev channel). So hopefully this will be fixed soon. I looked at the issue, and it is really strange as the browser renders things out-of-order compared to what is in the DOM. To get around this, add the xxf:element="div" attribute on the <xf:group> around the <fr:tinymce>. This tells the XForms engine to generate a div for the group, instead of a span. Now, generating a span in that case is not technically correct, as it contains a div produced by the TinyMCE. While not correct, in general this doesn't cause any issue. (This is actually the first time I see a real issue which seems to be caused by this.) Still groups should be smarter and generate a div or span depending on the content. We had a quick brainstorm about this, and think we came up with a good algorithm; see the comment on: https://github.com/orbeon/orbeon-forms/issues/1241 In the meantime, in cases like this, you can always manually specify you want the group to generate a div with xxf:element="div". You'll let us know if this works for you, Alex
--
Follow Orbeon on Twitter: @orbeon Follow me on Twitter: @avernet |
Hi Alex,
That indeed fixes the problem. We are happy with this workaround. Thanks for the quick response. Kind regards, Tars Joris. |
Free forum by Nabble | Edit this page |