You can trigger an installable build for these changes by visiting CircleCI here.

You can trigger optional UI/connected tests for these changes by visiting CircleCI here.

I would say that what we provide now is best described as the ability to edit block settings for unsupported blocks.

@guarani I don’t think this is only block settings, is it? From what I can tell, we aren’t placing special restrictions (other than hiding a few menu items) on what the user can edit on the canvas, so I don’t see a reason to frame it in that way.

For example, let’s say there is some sort of third-party text-based block that we don’t yet support out-of-the-box on mobile. If they use this function to open the block in the web view, they should be able to edit almost any aspect of that blocks contents, correct? Perhaps I am missing something?

@guarani I don’t think this is only block settings, is it? From what I can tell, we aren’t placing special restrictions (other than hiding a few menu items) on what the user can edit on the canvas, so I don’t see a reason to frame it in that way.

For example, let’s say there is some sort of third-party text-based block that we don’t yet support out-of-the-box on mobile. If they use this function to open the block in the web view, they should be able to edit almost any aspect of that blocks contents, correct? Perhaps I am missing something?

You're right, it's more than just block settings – I wasn't thinking past blocks similar to the video block which just have settings and no text content.

Ah ok, no worries — just wanted to make sure I wasn't missing something 😆

@iamthomasbishop - @guarani

Do we have access to the "spinner" that the web often uses (this one)? If not, we can do something like @etoledom mentioned and use the progress indicator we use on Preview.

I have implemented the Preview's loading indicator, since this is a native component we don't have easy access to it.

Hey! I'm moving this to 15.0 because 14.9 has been cut. If you want this to make it to 14.9, please feel free to ping me.

@etoledom I took the liberty of updating the milestone to 15.1 since 15.0 is about to be cut.

Updated this branch with current develop and gutenberg pointing to gutenberg-mobile:develop.

@guarani - would you mind doing a last smoke test?

• With metro running on gutenberg-mobile:develop:
  • Unsupported block feature should work as expected.
• Running Gutenberg from bundle (no metro running):
  • No option to open the web view on unsupported blocks should be visible.
  • Check that there are no errors or red screens.

Thanks!

@etoledom – I got this working, but at first I was getting the login screen on a .com site on the simulator. On my phone I got a blank screen and noticed this error in the Xcode console:

Please update the following components: withAnimatable(Component)
Error Domain=WKErrorDomain Code=4 "A JavaScript exception occurred" UserInfo={WKJavaScriptExceptionLineNumber=1, WKJavaScriptExceptionMessage=TypeError: undefined is not a function (near '...window.insertBlock...'), WKJavaScriptExceptionColumnNumber=19, WKJavaScriptExceptionSourceURL=undefined, NSLocalizedDescription=A JavaScript exception occurred}

I reinstalled and it started working on the same device, but the error was still shown on the console. This error didn't seem to stop changes from being made to the unsupported block.

Please update the following components: withAnimatable(Component)

This seems to be related to the bottom sheet in general, not to this feature in particular.

Error Domain=WKErrorDomain Code=4 "A JavaScript exception occurred" UserInfo={WKJavaScriptExceptionLineNumber=1, WKJavaScriptExceptionMessage=TypeError: undefined is not a function (near '...window.insertBlock...'), WKJavaScriptExceptionColumnNumber=19, WKJavaScriptExceptionSourceURL=undefined, NSLocalizedDescription=A JavaScript exception occurred}

This happens usually on .com, since there's an attempt to insert the block on page load, but the editor is not ready yet. There's a second attempt later on that will succeed.

Merging to bring the gutenberg bridge changes to WPiOS.
The new feature still is under dev-flag on gutenberg-mobile side.