Not sure if I understand correctly:

Not sure about the first one, tested a couple UIs here, some do in fact consider scrolling as a immediate change in cursor position (thus start dragging -- QTCreator tree view), some dont (nautilus tree view, GTK tree view).
However all of them allow to drag after scrolling stopped.

This was fixed by rBb4051db4fc3a

It is also the other way around (you can e.g. see Shader To RGB in cycles), so it is a general issue of uiTemplateNodeView I guess

Well.. it is looking here //..\..\..\ASSETS\txt_dlazdice_01_v1.png
Thats 3 folders up from where your blend file is, then the ASSETS folder, inside should be txt_dlazdice_01_v1.png

This is already fixed in current master, see T67973, please try a new build.

Well this is really not a place to ask about blender usage, please use one of these for this:
https://www.blender.org/Community/

This is the backtracke for deleting a whole particle, then Undo (cannot reproduce an Undo crash if I only delete a particle key...)
There, some ParticleCacheKey is broken...

Blender, you keep confusing me.

Interesting, will have a quick look...

If necessary I send the file.

Please do that, yes

There is no light in this file...

Can confirm

CC @Campbell Barton (campbellbarton)

Check discussion in D5485 also [efficient poll vs. invoke etc CC @Campbell Barton (campbellbarton) ].

I recall other issues with data paths in Shader Nodetree .
@Alexander Gavrilov (angavrilov) : havent checked code, but this was a bit special, right?

Can confirm on very first MMB drag.
As soon it is released, it works on second use for me though...

Guess this is due to recent changes by @Germano Cavalcante (mano-wii) (not sure though...)?

@Peter Keis (BlenderPeter) :
On MS-Windows: Download this dll and copy it so its located in the same directory as 'blender.exe' and run Blender normally.
(remember to remove it after the test)
This will run blender with Software OpenGL renderer [much slower, but helps determining if this a GPU/driver issue or something in blender code...]

I think there was a recent fix related to this, crash is resolved for me.

neither in the default viewport tab nor in the render tab, nowhere, but in the lower part of the window

Havent checked code, but to me ScrArea-flag HEADER_NO_PULLDOWN should be preserved?
(this is not only the case for startup blend, this is true for all saved .blends...)
Not sure if there is a reason to not do this?

cannot reproduce, dont have issues installing zipped Addons in 2.80 or 2.81 master.

This is also related to the sorting problem, see https://docs.blender.org/manual/en/dev/render/eevee/materials/settings.html#sorting-problem.
Similar as mentioned in T68956.
Not sure why you would use an Alpha Blend mode if you want Alpha=1.0?
But I have seen this reported before tbh.
I assume determining the overall Alpha in a (complex) shader tree could be quite a hassle, so doing this "behind the scenes" might not be considered atm.
So to me this doesnt look like a bug.

@Clément Foucault (fclem): does this ring a bell?

Looks like typical sorting problem with Alpha Blend mode? See https://docs.blender.org/manual/en/dev/render/eevee/materials/settings.html#sorting-problem
If you dont need real lighting in your shader you can use the Transparent BSDF node, that suffers from the same sorting problem internally, but is not noticable.

@dark999 (dark999): Assume this is about the Wireframe Shading Node.

Assume this is confirmed (havent checked myself though)

Hm, iirc disabled pretty much enforces unselected in 2.8.
So even if we disable the check here https://developer.blender.org/diffusion/B/browse/master/source/blender/editors/animation/anim_filter.c$3026, we still dont get the hidden object included in the dopesheet.

Could you check if upgrading your drivers fixes the problem? https://downloadcenter.intel.com/product/98909/Intel-HD-Graphics-630

Ah, here we go, I can reproduce loading having Load UI ON.
Thx everyone for poking.
[ still cannot reproduce having Load UI OFF -- even though in SOLID, but I guess that is not mandatory for calling this a bug :) ]

Can confirm what @Jesse Y (deadpin) said (thx investigating!)

note this also happens for shaderfx rim/shadow offset
rim/shadow blur also behave weird (dont increment/decrement using arrows)