Skip to main content
Known Participant
November 24, 2017
Answered

Incorrect cursor tabbing through expanded wrapped HTML via Emmet?

  • November 24, 2017
  • 3 replies
  • 967 views

Hi. Recently came back to DW for coding and I'm so very pleasantly surprised. New functionality, Emmet functionality, super! But have one issue in Emmet... while "tab" expands HTML abbreviations correctly for me, what I'm used to from other code editors is then being able to tab in between tag wrappers so I can easily jump from <li> to <li> for example. But in my case tab is expanding my first content into a tag for that content, instead of going say from <li> to <li>. Is there a setting for this behavior or a temporary disable of tab expansion? Example:

ul>li*5 expands correctly into:

<ul>

   <li>[cursor defaults to here]</li>

   <li></li>

   <li></li>

   <li></li>

   <li></li>

</ul>

and puts my cursor at the first <li>. But say I enter

<li>Element1[cursor is now here]</li>

And then tab... instead of the cursor moving to the next logical <li> insertion point, it expands my most recent content, Emmet-style:

<li><Element1>[cursor now here]</Element1></li>.

It's expanded my content into a tag.

Any help here? Thank you.

    This topic has been closed for replies.
    Correct answer Jon Fritz

    With Emmet turned on, any time you hit Tab after typing a word, it will turn that word into a set of <that_word></that_word> tags. it's just the way Emmet in DW works.

    DW has never moved "to the next logical _x_ insertion point" with the Tab key in Code View either way. Prior to Emmet being added, hitting Tab would create a tabbed indent in the code.

    3 replies

    Jon Fritz
    Community Expert
    Jon FritzCommunity ExpertCorrect answer
    Community Expert
    November 27, 2017

    With Emmet turned on, any time you hit Tab after typing a word, it will turn that word into a set of <that_word></that_word> tags. it's just the way Emmet in DW works.

    DW has never moved "to the next logical _x_ insertion point" with the Tab key in Code View either way. Prior to Emmet being added, hitting Tab would create a tabbed indent in the code.

    B i r n o u
    Legend
    November 25, 2017

    I've posted different features request in alpha and CAB forums, because emmet is not well implemented in DW, and cause troubleSSS for user using emmet in different other code editor... and as it should

    so to answer your question, I don't think that there are any settings (perhaps some hidden ones, but I'm noit aware of it)... and emmet is badly implemented in dw

    Nancy OShea
    Community Expert
    Community Expert
    November 25, 2017

    Yes, Emmet is not fully supported in DW as it might be in other text editors.  Which is why I suggested switching to Design view and using the ENTER key. 

    Nancy O'Shea— Product User & Community Expert
    B i r n o u
    Legend
    November 25, 2017

    what is the main goal of being in code view using emmet, and the have to move in design view to still enter content ? I miss the point???

    Nancy OShea
    Community Expert
    Community Expert
    November 24, 2017

    If I'm understanding correctly, you can switch from code to Design View and hit Enter to create another list element.

    Nancy O'Shea— Product User & Community Expert
    Known Participant
    November 25, 2017

    This is not the correct answer; I don't know why it was marked that way. This doesn't even address the question.

    I appreciate someone trying to help out so was going to let it go and apologize if my original question was unclear. But this has nothing to do with design view and someone marked this as the correct answer so am jumping in. The issue I described has to do with Emmet, the system used in code view for expanding abbreviations into HTML.