Setting twig.debug to true (services.yml) seems to break the display/opening of JS dialogs for
field settings (format) in views ui (/admin/structure/views/view/xxxx/edit/yyyy)
→ In my case a REST Export view for nodes referenced by taxonomy.

We've added some node fields to Format > Fields. Every AJAX dialog within the view then was broken - failing silently with no error messages (JavaScript, watchdog etc.)

Disabling the twig debug mode fixed this.

Comments

seppelM created an issue. See original summary.

cilefen’s picture

Priority: Major » Normal

Since this affects the admin UI only and there is a workaround (disabling debug), this is not major priority.

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

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

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

joelpittet’s picture

Issue tags: +JavaScript

Maybe we can strip HTML comments before output or store them somewhere else if going to JS and swap that based on the services setting... Can you point out which JS file is responsible for displaying the text/markup output?

droplet’s picture

Sounds impossible. I've done a quick test and didn't find the problem. Could you post more detail steps with the standard default view?

there're some issue about dialogs will not open in some conditions that may be related.

joelpittet’s picture

Status: Active » Postponed (maintainer needs more info)
Issue tags: +Needs steps to reproduce

postponing details from #5

dawehner’s picture

Ideally the next steps would be a clear step by step instructions how to reproduce it.

joelpittet’s picture

Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

To triage the issue queue I'm closing this. Feel free to re-open with steps to reproduce the problem.

seppelM’s picture

We weren't able to reproduce the "bug" in 8.20 so far.

joelpittet’s picture

Thanks for the feedback @seppelM. Sorry you can't re-open but I can if need be. It's a recent change that I didn't realize while closing.