Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-2358

JSF proposal replaces wrong part of text when inserted into non-ended attribute value.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 2.1.2, 3.0.0.alpha
    • 2.0.1, 2.1.1, 3.0.0.alpha
    • None
    • None

      JSF-prompting proposal replaces wrong part of the text when inserted into non-ended attribute value.

      Create a Seam project, open home.xhtml file in JBoss Tools HTML editor. Type-in the following text:

      <h:outputText style="" value="#{a />

      Then place the cursor right after "value=#{a" (there shouldn't be a closing quote-char in the attribute value) and press Ctrl-space to invoke the content assistant. Select "applicationScope" from the list and press Enter.

      As the result the text will be: <h:outputText style="" value="#

      {aapplicationScope}"/> (The initial "a"-character was not replaced while the next space characted has eaten by the replacement)

      The same result occures if the initial text is somehow longer then one character, for example, if you'll type "<h:outputText style="" value="#{appli />" and then apply the "applicationScope" JSF-proposal, then the result will be exactly the same: <h:outputText style="" value="#{aapplicationScope}

      "/>

      Test Case:

      EXECUTE: Create a Seam project.
      EXECUTE: Open home.xhtml file in JBoss Tools HTML editor.
      EXECUTE: Type-in the following text: <h:outputText style="" value="#{a />
      (Do not close the quotes in the attribute value)
      EXECUTE: Press Ctrl-Space to invoke the Content Assistant, select "applicationScope" JSF-proposal from the list and press Enter
      ASSERT: the new attribute value is inserted correctly, all the other chars are stood as they were typed-in.

              vrubezhny Victor Rubezhny (Inactive)
              vrubezhny Victor Rubezhny (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: