LinkedIn Tool

Minor enhancements to LinkedIn. Mostly just hotkeys.

יש גרסאות של סקריפט זה עם קוד מעודכן. הצג את כל הגרסאות

  • v1.0.0 01-08-2023

    Support the /notifications/ page.

    Adds navigating up and down posts, opening the menu, and activating the notification (same as click on it).

    Not perfect, but works well enough to ship and get feedback.

    I had most of my notifications turned off, so I am unable to test against most of them. And it appears that almost every notification has a different way of activating it. So I'm sure I missed many.

    Supporting a new page warrants a bump in the major version number.

    Closes #35.

  • v0.20.2 01-08-2023

    Reflow and improve some comments., Switch to only tracking focus events for disabling hotkeys.

    The previous implementation depended on catching blur events to determine if a user left an input field so that hotkeys could be reenabled. However, it turns out that those events will not be fired if the focused element is destroyed. When a focused element is destroyed, focus will change, causing another focus event, so that can be used to see what really happened.

    Did involved introducing a new global variable, but really, that is what setContext is doing anyway, just hidden.

    Closes #36.

  • v0.20.1 31-07-2023

    Do not focus on the post if it is already the one we are reading.

    Mostly for when loading comments, we keep our current position rather than popping back to the top of the post.

    Usually I'm not a big fan of early returns, but the function is small enough I think it is all right for now.

    Closes #28.

  • v0.20 31-07-2023

    Use the f key to change the browser focus to the current item.

    We were intentially not updating the browser focus because it requires adding tabindex the the element, and apparently that is bad form, accessibility wise. However, there are times when it is useful. So this will temporarily update tabindex, focus, then drop tabindex.

    Closes #33.

  • v0.19 31-07-2023

    Handle the case where the element passed to inInput does not have a tagName.

    Not sure if this is because of the previous change, or I just never noticed this before. Sometimes the element passed to isInput is document, which does not have a tagName property. And referring to it would throw exceptions. Really all this does is makes sure not to clutter the log., Support the = to bring up a nearby menu.

    I wanted to use the - key, but the library I'm using doesn't support that. Bummer.

    Closes #32.

  • v0.18.5 31-07-2023

    Make the isInput function a bit more robust.

    It now handles textarea as well as input fields.

    I have not come across any textareas on LI, but because of the converstation on https://github.com/violentmonkey/vm-shortcut/issues/10, I decided to update it.

  • v0.18.4 31-07-2023

    Just a version change to trigger a push to openuserjs (take 2).

  • v0.18.3 31-07-2023

    Just a version change to trigger a push to openuserjs.

  • v0.18.2 31-07-2023

    Update @supportURL to point to newly written documentation.

    Also update @description to match the new docs.

  • v0.18.1 30-07-2023

    Add license to the source file.

  • v0.18 30-07-2023 Imported from URL

Show all script versions