You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issue by njx Wednesday May 07, 2014 at 19:41 GMT Originally opened as adobe/brackets#7775
For #7764. This isn't the cleanest fix, but it exactly preserves the existing behavior for the case where getModeForRange() is called from getModeForSelection(), while fixing the behavior for the case where getModeForRange() is called directly from the commenting operations in EditorCommandHandlers.
The EditorCommandHandlers unit tests all pass with this fix.
Issue by njx
Wednesday May 07, 2014 at 19:41 GMT
Originally opened as adobe/brackets#7775
For #7764. This isn't the cleanest fix, but it exactly preserves the existing behavior for the case where
getModeForRange()
is called fromgetModeForSelection()
, while fixing the behavior for the case wheregetModeForRange()
is called directly from the commenting operations in EditorCommandHandlers.The EditorCommandHandlers unit tests all pass with this fix.
@
peterflynn /cc@
TomMalbrannjx included the following code: https://github.com/adobe/brackets/pull/7775/commits
The text was updated successfully, but these errors were encountered: