Description: First, you need to have a place I can upload a fucking picture, because it is worth a million words and I wouldn't have to waste my time writing this and your time reading it. Pretend that this is the screen is a matrix, which it is, like so: ooooo... ooooo... ooooo... . . . In any Libre Office App in the Suite, I have to click BELOW the spot I want to click in order to actually click the desired button, menu, or whatever object....Even a word on the "page". There is a very good point to using a pointer, and that is to actually point at the thing you click at so that you know what you are clicking. I expect when I place my pointer on the "x" below and click, that the same spot (with an "x") in row 2 will be "clicked" inside the software: 1st row ==> ooooo 2nd row ==> ooxoo 3rd row ==> ooooo Well, that simply does NOT happen. This is what happens instead: The "y" below represents the spot "clicked" by the software when the pointer is placed at the spot with the "x". 1st row ==> ooyoo 2nd row ==> ooxoo 3rd row ==> ooooo So, that fundamental pointer-to-click syncronization is broken in your product. I am surprised you haven't seen this before. I am using Windows 10 on an Intel NUC w/ Intel i7. Fix it or I am moving on. Great idea, but non-functional is non-function, whether it is free or not :/ Steps to Reproduce: 1. Read the description above 2. Work on the ability to accept photo uploads...It IS 2017 ... 3. Test before releasing Actual Results: above Expected Results: above Reproducible: Always User Profile Reset: What? Additional Info: Again. Photo Upload User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36
Hello, you can add an image as an attachment... To be certain the reported issue is not related to corruption in the user profile, could you please reset your Libreoffice profile ( https://wiki.documentfoundation.org/UserProfile ) and re-test? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the issue is still present
*** This bug has been marked as a duplicate of bug 110438 ***