This behavior is still present in current builds and can result in pretty nasty bugs and performance related crashes. Assigning @Dalai Felinto (dfelinto) upon his twitter comment.

Unfortunately this feature breaks shading for hard surface objects.
https://devtalk.blender.org/t/problem-with-rendering-matcaps-after-perspective-fix/1979

Thanks!
Radius of 2 pixels produce quite blurry image imho. 1 px radius bumps smallest details as intended. For big and medium forms we can use SSAO cavity. Both effects works great in conjunction.

If I may suggest something. Button responsible for flipping should be a bool toggle, with blue background if matcap is flipped. This way users will know if they are viewing matcap oriented like in image file or flipped. This may be handy in matcap creation process.

I cannot agree with this design. Issue is not where to place those "kinda-global" settings but the fact that they are global. This makes absolutely no sense from workflow perspective. We need to have in mind that editors that use those options operate on entirely different contexts and require different workflows. Referring to @Julian Eisel (Severin) post, how can we possibly put all snapping options in one global list? What will happen when user select "Node Y" and work in 3D View or selects "Volume" option and work in UV Editor? Current behavior is subject of complains from community and this design will make it only worse.

Tested on latest build and bug is still present. It turns out object doesn't need to have Shrinkwrap modifier. Individual origins and enabled Proportional editing still apply.

+1 for simplicity.
People don't use TexFace mapping these days because it's not compatible with Cycles, external render and game engines. If people really need to bring back old BI scenes to 2.8 they can download 2.79 and convert them easily. We might think of providing official addon for 2.79 that do this automatically.

I don't think fusing OS title bar with our top-bar is good idea. Lack of blend filepath and save status would be a significant drawback. Where that will go?

Thanks for clarifying. I was asking because I actually have brief idea how this might be solved, but since this task is closed I'm not sure where to post it. Should I send it to mailing lists or start new design task under someones permission?

The new manipulator oriented tool workflow (of course the shortcut oriented one will still be there)

Thank you @Julian Eisel (Severin)! :) I think people will like new logic for this slider, it works good in other programs.

@Joshua Leung (aligorith) That's a relief. ;)

Is this planed to work in all blender areas or exclusively in pose mode?

I also not fan of preserving 'visibility bits'. This will be very confusing and super error-prone. While managing scene users must not only take care of layers but also set up this visibility bits. This is basically forcing users to do same task twice, every time he move objects between layers. We can just use sub-layers for similar behavior but make everything clear, intuitive and familiar.

Didn't tested that. Thanks.
On 2.76 jiggling still happen but only on boolean intersection.
Both in 2.76 and current master Decimation set to Collapse works fine, topology stays intact.

@Aaron Carlisle (Blendify) - Today on IRC Sergey pointed me to assign this task to him. This issue is not necessarily related to addon itself. Will add Greg and Bartek as subscribers but reassigning this back to @Sergey Sharybin (sergey).