Incompatibilities between Sharepoint 2013, SPD2013 and Office 2010

I recently had a gig where I was using Office 2010 tools (Word, Excel, PowerPoint, InfoPath and Visio) in a SharePoint 2013 on-prem environment.  I discovered a couple of weird incompatibilities (or "features").  The environment I used had no CU's or hot fixes and SP1 was not installed.   I've not had the opportunity to test this with Office 365.

1.  Using InfoPath 2010:  So long as I only had Office 2010 products on my laptop, I was able to successfully create an InfoPath form in a list and display it on a web part page.  However, once SPD2013 was loaded onto my laptop, I was no longer able to use InfoPath 2010.

Proposed solution:  Isolate:  Use a VM environment with Office 2010 only products or with SPD2013 (probably the better choice).

2.  The presence of SPD2013 no longer enables a user to click on a document and use it in SharePoint.  The presence of SPD2013 requires that user to download the document.  This makes it difficult for a developer to have the end user experience.  Isolating SPD2013 in a VM may be the best way to work.

I would love to know the logic behind this "feature".

3.  The Drag and Drop Feature:  I was able to drag and drop documents, but my end users couldn't.  We were using IE8.  The difference was the presence of SPD2013 on my computer.  A little digging on the net uncovered the following:

If you are using IE10 or later, Firefox or Chrome, you are ok.
If you're using IE8 or IE9, you need some component of Office 2013 (in my case, SPD2013) installed.  See:

SharePoint Server 2013: Drag and drop contents to Library
This is due to the use of HTML5:
SharePoint 2013: Unable to Drag and Drop Files in Document Libraries

Keep this in mind as you develop training materials for your end users:  they may not be able to use this most awesome feature.

That's all I've observed so far.  Let me know if you have any other Office 2010/SPD2013/SharePoint 2013 incompatibilities.