Language variant split view - editorState.getCurrent().variants active out of sync
See original GitHub issueI am writing a back-office plug-in and using the active
property of the editorState.getCurrent().variants
array to determine which variant is used.
This works fine until you open a variant in split view. The active variant is the one that was already opened instead of the one you open in split view.
This is with umbraco v8.6.0
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (3 by maintainers)
Top Results From Across the Web
platform/system/core
+ * See the License for the specific language governing permissions and + * limitations under the License. + */ + +#ifndef __CUTILS_BITOPS_H...
Read more >Bug List
contrainShellSize() not working correctly for multiple workspaces, 2005-05-10 ... [Progress] Dual Screen setup: Progress dialogs show up on wrong screen ...
Read more >https://opensource.apple.com/source/WebKit/WebKit-...
2015-08-19 Brent Fulgham <bfulgham@apple.com> [Win] Replace MIDL [in/out] ... 2015-04-09 Chris Dumez <cdumez@apple.com> [WK2][iOS] editorState() should not ...
Read more >togethercomputer/RedPajama-Data-1T-Sample · Datasets at ...
The wait is triggered when an instance of // this class goes out of scope. class ThemeChangeWaiter { public: explicit ThemeChangeWaiter(ThemeService* ...
Read more >VIM -- VI-style Editor with folding capabilities
This paper tried to introduce a new concept: orthodox editors as a special category of editors that have command line set of command...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@umbrabot still relevant Still waiting for the “I’ll have to ask around and get back to you.” part 😃
Hiya @stefankip,
Just wanted to let you know that we noticed that this issue got a bit stale and might not be relevant any more.
We will close this issue for now but we’re happy to open it up again if you think it’s still relevant (for example: it’s a feature request that’s not yet implemented, or it’s a bug that’s not yet been fixed).
To open it this issue up again, you can write
@umbrabot still relevant
in a new comment as the first line. It would be super helpful for us if on the next line you could let us know why you think it’s still relevant.For example:
This will reopen the issue in the next few hours.
Thanks, from your friendly Umbraco GitHub bot 🤖 🙂