Will archive for now then (feel free to comment again if you have found a way to reproduce...)

Sorry Campbell, I can't give anything about my previous moves but as far as i remember was just extruding and scaling thats all. I was exactly repeating the process on this video in Blender Cloud. https://cloud.blender.org/p/blenderella/56040ecf044a2a00a515adaa

@Jacques Lucke (JacquesLucke) I'm sorry. I take back my words. However, this is not the correct behavior of blender, this should not be. Thank you!

Since last asking for information it has been 7 or more days, due to the policy of our bug tracker we will have to archive the report until the requested information is given.

@Jacques Lucke (JacquesLucke) Alas, nothing is working as it should. The face should not be inserted at all properly. I can make another video, or you can try it yourself to explore what comes out of it.

Looks like everything is working as it should, except that the default thickness for Inset is 10mm. This is way to large for this small object. If you reduce it by moving the mouse away from the face center, it behaves normally.
The fix is probably to make the default thickness dependent on the selected face size.

I'm the one who started this thread, and as @Rainer Trummer (aliasguru) says, I am not a blender developper anymore. Back in 2014, it seemed any work on new modifiers was prohibited because a change of paradigm towards node-based modifiers was envisaged. I had built a 'randomizer' modifier that was trashed for that reason.

@Rainer Trummer (aliasguru)
The dev who started this thread also unassigned and unsubscribed himself from the topic almost 3 years ago.

Also from our side at the studio a very much longed for modifier! Are there plans to go ahead with this proposal?

The smoothing algorithm here is pretty poor, but improving that is outside the scope of the bug tracker.

I can confirm that, however since this never worked, it might even work like intended and this is a feature request. Not Sure. @Brecht Van Lommel (brecht), do you know more?

Seems to be somewhat dependent on scale (precission issue). If I scale it up in eitmode 10 times, inset seems to behave normally...
Confirming for now...

This seems to be cause the operator does not properly keep track of the locked axis. You can seen that the Z axis is still ticked. If you untick it and then hit shift+r, it works.

Made some corrections to F2 code so it's the same as official.
Moved the addon panel to the right menu with it's own tab.

Just found this amazing tool while searching for F2 alternatives.
But it lacked a port to 2.80, so i did it.

Was fixed rB7d8f57e0c013ef43d4d1f1b7afd0477d690e70c5

2.8 have changed since this report was made.
The crashing are still happening in this very specific and odd situation but to reproduce the error now it has to be clarified in the steps above that you change to Sculpt mode through the "object interaction mode" menu at the up left corner of the screen.

The options actually work, just the operator is not executed again. (it updates when you click on "Deselect" twice)

thank you - it worked for me,after when i applied scale to my object

how i am supposed to add scale and why is it important,when i create bevel edges?

@Szymon Warunek (szymi) Hi.
I downloaded file and as I thought the problem is that you forget to apply scale to your object.

thank you dear developers - this issue is fixed,it works now

thank you for fixing this issue,i must check the newest build,to make sure this was fixed.

The problem was:

1. That the UVs are not selected and you have to activate "All UVs" to also export non-selected uvs.
2. There was a bug in the addon that it only exports the selected objects, however the object you have in edit mode is active, but not selected. Fixed that.

Probably was re-introduced by rBd3e0d7f0825. Would need to have a closer look and ensure that LIB_ID_COPY_RUNTIME is only used inside of the modifier stack, but not when creating mesh for the first result.
Tomorrow is more fixes :)

Hi Sergey,

Don't know if this is in the tool department or UI department. So I'll assign you because I'm guessing this is the UI and not tool specific.

This is the solution that came to my mind (but I did not consider all cases):

diff --git a/source/blender/draw/intern/draw_cache_impl_mesh.c b/source/blender/draw/intern/draw_cache_impl_mesh.c
index 3037a2fe225..c7b5c4853c2 100644
--- a/source/blender/draw/intern/draw_cache_impl_mesh.c
+++ b/source/blender/draw/intern/draw_cache_impl_mesh.c
@@ -474,8 +474,8 @@ static MeshRenderData *mesh_render_data_create_ex(
 			rdata->mapped.l_origindex = CustomData_get_layer(&me_cage->ldata, CD_ORIGINDEX);
 			rdata->mapped.p_origindex = CustomData_get_layer(&me_cage->pdata, CD_ORIGINDEX);
 			rdata->mapped.supported = (
-			        rdata->mapped.v_origindex &&
-			        rdata->mapped.e_origindex &&
+			        rdata->mapped.v_origindex ||
+			        rdata->mapped.e_origindex ||
 			        rdata->mapped.p_origindex);
 		}

Hello ,
I did short video compare between 2.79 and 2.8 for Mesh Circle Curve how its work during in subdivision modifier smooth and quad toggle in 2.79 its work fine smooth toggle but in 2.8 still not work in smooth toggle in edit mode .
Please check video example.
Thank you.
Regards.
Pierre