Wow. So, what do you think of everything I've done?
Also, what page are you on now? I'm on page 26.
Remember to reference POST number instead page number as there are 10 different "posts per page" settings. Although I can easily convert in my head since I'm on 100 posts per page vs the default 10.
TwoCables I must say I am a little disappointed in your lack of vision for the proposed menu changes. There is no need to block the entire area which prevents clicking subscriptions and messages. I am not sure what you know how to do, so I'll list a few ways I can think of making this possible.
First off, the way these types menu's open and close is an issue that was fixed in the 90's by Apple(?), and yet coders all over the planet do not make menu's correctly in 2016! They fixed it by detecting the vector of your mouse and if it were heading TOWARD the menu at a certain angle and acceleration the menu would stay open. I highly doubt that that is even possible with this simple web code though, so the behavior will have to be emulated as best as possible.
Our menu behavior end goal is:
To prevent the menu from closing unintentionally if moving from the profile picture to it diagonally.
We don't know how to make a delay which would have been the easiest solution.
I'm also going to stay on the safe side and assume that implimenting something like this this interferes with the ability to click something beneath.
If we can do anything resembling diagonals then this should be completly possible.
Here I have drawn three lines.
Green would work if it did not interfere with the words. I'm going to assume that there is interference and rule out green.
Yellow will work if the lines that the words are on which are continue invisibly can be trimmed or perhaps that's not even necessary and they can just simply be covered. The downside is that you cannot click the number for Subscriptions directly, and thus you'd want to make the number for private messages match. I find that 95% of diagonal entries fall within yellow.
The third line Red is the worst case scenario line. It will probably be very limited in it's effectiveness, likely to the point of not even being noticed or used 90%+ of the time.
So can we adapt the code to go diagonally instead of straight? That is THE most important question.
NOTE: The angle of the line is just eyeballed. It should probably be adjusted for technical and or functional reasons.
Edited by cookieboyeli - 1/25/16 at 3:53pm