ICEfaces
  1. ICEfaces
  2. ICE-11326

Add id to text area in ace:richTextEntry

    Details

    • Type: Task Task
    • Status: Closed
    • Priority: Major Major
    • Resolution: Won't Fix
    • Affects Version/s: 4.2
    • Fix Version/s: EE-4.2.0.GA
    • Component/s: ACE-Components
    • Labels:
      None
    • Environment:
      ICEfaces 4 trunk r51638, Tomcat 8, all browsers
    • Assignee Priority:
      P2

      Description

      There is nothing functionally wrong with the component. For automated testing purposes it would be nice to be able to extract an id from the text input area that we can work with. The top and bottom of the richTextEntry have an id such as cke_top, cke_bottom, can the same be done for the text input area?

        Activity

        Hide
        Arturo Zambrano added a comment -

        Do you mean the actual area that displays the content? The internal <textarea> element is already rendered with an ID, which is preserved after CKEditor initializes in the client. So, I suppose you want to access the actual area where the text is displayed with all the formatting, etc. Right? If that's the case, we would have to modify the CKEditor code to apply an ID to it, but I'm not sure that would really help, since all that area is inside an iframe, and often times it's not possible to access anything inside an iframe from the outside/host page. This area is actually the 'body' element of the iframe, so you might want to try first to access it by specifying this body element inside the iframe, or you can try to access it by specifying the 'cke_editable' CSS class as a selector. If it's not possible to access elements other than by ID, from the testing scripts, then we can try adding an ID and see if it works that way.

        Show
        Arturo Zambrano added a comment - Do you mean the actual area that displays the content? The internal <textarea> element is already rendered with an ID, which is preserved after CKEditor initializes in the client. So, I suppose you want to access the actual area where the text is displayed with all the formatting, etc. Right? If that's the case, we would have to modify the CKEditor code to apply an ID to it, but I'm not sure that would really help, since all that area is inside an iframe, and often times it's not possible to access anything inside an iframe from the outside/host page. This area is actually the 'body' element of the iframe, so you might want to try first to access it by specifying this body element inside the iframe, or you can try to access it by specifying the 'cke_editable' CSS class as a selector. If it's not possible to access elements other than by ID, from the testing scripts, then we can try adding an ID and see if it works that way.
        Hide
        Liana Munroe added a comment -

        I have found a way to force webdriver to switch to the iframe then use Javascript Executor to edit the inner html so that I can enter and submit content. For now I can use this workaround.

        Show
        Liana Munroe added a comment - I have found a way to force webdriver to switch to the iframe then use Javascript Executor to edit the inner html so that I can enter and submit content. For now I can use this workaround.

          People

          • Assignee:
            Arturo Zambrano
            Reporter:
            Liana Munroe
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: