Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Leaving a boundary such as a <code> tag can move you to the next block #2993

Closed
2 tasks
aaronjorbin opened this issue Oct 12, 2017 · 5 comments
Closed
2 tasks
Labels
[Type] Bug An existing feature does not function as intended

Comments

@aaronjorbin
Copy link
Member

Gutenberg Version: 1.4

Issue Overview

If a paragraph block has a <code> boundary as the last item, and there is a paragraph block after it, pressing the right arrow moves you to the next block. I would expect to

Steps to Reproduce (for bugs)

  1. Create two paragraph blocks
  2. In the first block, create a code tag using \word``
  3. Reenter the code boundary
  4. press the right arrow key

Expected Behavior

I expect to stay in the block that I am currently writing in

Current Behavior

I move to the next block.

Possible Solution

Related Issues and/or PRs

Todos

  • Tests
  • Documentation
@youknowriad youknowriad added the [Type] Bug An existing feature does not function as intended label Oct 12, 2017
@karmatosed karmatosed added this to the Merge Proposal milestone Jan 25, 2018
@jorgefilipecosta jorgefilipecosta modified the milestones: Merge Proposal, Bonus Features Mar 22, 2018
@jeffpaul
Copy link
Member

This ticket was mentioned in Slack in #core-editor by jeffpaul. View the logs.

@ZebulanStanphill
Copy link
Member

This is a duplicate of #1246 isn't it? Then again, #1246 is not as broad, though it appears that there is just one generic issue with inline boundaries that is not limited to just links. Maybe #1246 should be closed in favor of this issue? And then there is #5095, which appears to also be a duplicate.

@jasmussen
Copy link
Contributor

I would agree with @SuperGeniusZeb that this ticket and #1246 seem to touch on the same, which is still an issue:

boundary

Just in order to keep things moving, I'm going to close the previous one in favor of this one as this seems more descriptive, though noting appreciation and gratitude to @buzztone for opening the original issue.

@ZebulanStanphill
Copy link
Member

@jasmussen What about #5095? Should it be closed in favor of this one or vice-versa? They appear to be about the same thing as well.

@jasmussen
Copy link
Contributor

jasmussen commented Apr 13, 2018

Good point, @SuperGeniusZeb, thank you.

Although this ticket was technically first, that other ticket has since then been added to the merge proposal milestone. And so I'm closing this one in favor of #5095. Apologies for the mess, but in cleaning this repo we can at times be a bit heavy handed. The issue will be fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Type] Bug An existing feature does not function as intended
Projects
None yet
Development

No branches or pull requests

7 participants