你正在訪問的內容是外部程式的映像位址,僅用於使用者加速訪問,本站無法保證其可靠性。當前的連結位址(單點即可複製)為 https://greasyfork.org.cn/zh-CN/scripts/472097-linkedin-tool,源站連結 點此以跳轉

LinkedIn Tool

Minor enhancements to LinkedIn. Mostly just hotkeys.

当前为 2023-10-18 提交的版本,查看 最新版本



點此查看下載連結位址https://update.greasyfork.org.cn/scripts/472097/1266693/LinkedIn%20Tool.user.js

安装此脚本?
作者
Mike Castle (Nexus)
评分
0 0 0
版本
5.5.2
创建于
2023-07-30
更新于
2023-10-18
大小
148.9 KB
许可证
GPL-3.0-or-later
适用于

LinkedIn Tool

Minor enhancements to LinkedIn. Mostly just hotkeys.

The major reason for this userscript is to provide keyboard navigation to LinkedIn.

A secondary reason is, being my first userscript, it provides me with a platform to learn HTML, JavaScript, CSS and other web technologies.

Mostly it works by mapping keystrokes to mouse event (e.g., hitting a key sequence results in a mouse click), or causing the page to scroll a bit of content into view. It currently does not collect or save any information, though future enhancements may provide some customization which would require that.

[!WARNING] 2023-10-16 A future change will enable storing information locally. This is primarly driven by issue https://github.com/nexushoratio/userscripts/issues/106, which will enable a News tab, which will be used to track which version a user has installed and provide them with a chance to read about new features. Other features, such as the ability to enable logging and debugging, will likely come along as well. The basic ability to save data locally will not be enabled before 2023-11-16 and we be marked by the @grant lines in the userscript header. Issue https://github.com/nexushoratio/userscripts/issues/170 has been created to track this and provide more information. Any major updates to the timeline will be provided there.

Installation

After installing and reloading the LinkedIn web page, hitting the ? key will bring up a help menu.

Feedback

Existing issues can be seen at GitHub.

New bugs and feature requests can be filed on GitHub. Select the appropriate issue template to get started.

Versioning

Currently I am using a SemVer inspired scheme of x.y.z.

  • x will be bumped whenever a new page is handled. 0 was for /feed/, 1 introduced /notification/ support.
  • `y' will be a new feature (e.g., new keystrokes)
  • z bumps are bug fixes or internal changes (refactorings and the like)