Problem/Motivation

When you edit a node with quickedit and without closing the toolbar, then use quickedit on another node. The quickedit toolbar will not show up.

Steps to reproduce:
1. Click Pencil to edit a node, and then click a field to edit
2. (Do nothing)
3. Click another Pencil to edit another node's field

Bug:
Quickedit toolbar does not popup, and see JS error in Console.

Expected:
Closing the old quickedit toolbar, and see new toolbar on new node's field.

Proposed resolution

- (TBA)

Remaining tasks

- (TBA)

User interface changes

- (TBA)

API changes

- (TBA)

Data model changes

- (TBA)

Comments

droplet created an issue. See original summary.

Wim Leers’s picture

It's intentional that you cannot edit multiple instances at the same time. It'd be too overwhelming. We'd have to manage two of the floating toolbars, and we can't position both well.

That being said, I think it is a bug that you can't go from quick editing one thing to another: that should not cause errors to be logged to the console.

Wim Leers’s picture

Status: Active » Postponed (maintainer needs more info)
droplet’s picture

Title: Can't edit multiple instances at same time » quickedit toolbar didn't shown when you edit another field without close current instance
Issue summary: View changes
Status: Postponed (maintainer needs more info) » Active
Issue tags: +JavaScript, +Needs JS testing

Updated IS.

It's intentional that you cannot edit multiple instances at the same time. It'd be too overwhelming. We'd have to manage two of the floating toolbars, and we can't position both well.

Yes. this makes senses. It just needed to close/reset current quickedit toolbar instance and start a new toolbar correctly

Wim Leers’s picture

Thanks, much better title :)

Wim Leers’s picture

Title: quickedit toolbar didn't shown when you edit another field without close current instance » QuickEdit toolbar doesn't show when starting to edit another entity without closing the current instance
Issue tags: +Usability

Although that was not quite correct yet. I think this is what you were going for.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.