Update unsupported block editor test cases#42
Conversation
Clarified wording around Jetpack connected self-hosted sites
| - The Unsupported Block Editor is currently [not available on Jetpack connected self-hosted sites](https://github.com/wordpress-mobile/gutenberg-mobile/issues/2471) | ||
|
|
||
| ### Self-hosted sites are supported | ||
| ### Self-hosted sites are supported (if they are not connected to WordPress via Jetpack) |
There was a problem hiding this comment.
👋 @guarani , when logging in the Jetpack .org site using username and password, does it matter if Jetpack is connected or not? The testcase makes it look like "not connected" is supported, but unsure about when connected.
Can we add a new testcase to cover the connected case, or rephrase that bit in the current testcase (say, by removing the mention to connected or not)?
There was a problem hiding this comment.
That's a good point. Now we've disabled self-hosted sites I'm going to go ahead and remove the test case entirely. (I think self-hosted sites were supported when the user used their username/password to log in.)
There was a problem hiding this comment.
I think self-hosted sites were supported when the user used their username/password to log in.
They were (before we found the issue with Classic editor popping up if Gutenberg is disabled) but I might be misunderstanding the testcase: when logging in with username/password the feature should actually have worked regardless of the Jetpack state (uninstalled, installed but not-connected, connected), right? 🤔
Removed new-line literals from Jetpack markdown sample HTML