Some of vimium's functions are not available because of security policies
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 27k
- Forks
- 2.6k
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
Blocked script execution in some page because the document's frame is sandboxed and the 'allow-scripts' permission is not set.
To Reproduce
- Go to URL 'https://raw.githubusercontent.com/philc/vimium/master/README.md'
- typed 'T' no responese
Console error
Blocked script execution in 'chrome-extension://dbepggeogbaibhgnhhndojpepiihcmeb/pages/help_dialog.html' because the document's frame is sandboxed and the 'allow-scripts' permission is not set.
README
Browser and Vimium version
Vimium version:1.66
| Google Chrome | 83.0.4103.116 (正式版本) （64 位） (cohort: Stable) |
|---|---|
| 修订版本 | 8f0c18b4dca9b6699eb629be0f51810c24fb6428-refs/branch-heads/4103@{#716} |
| 操作系统 | Windows 10 OS Version 2004 (Build 19041.329) |
| JavaScript | V8 8.3.110.13 |
| Flash | 32.0.0.387 C:\Users\wlei3\AppData\Local\Google\Chrome\User Data\PepperFlash\32.0.0.387\pepflashplayer.dll |
| 用户代理 | Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.116 Safari/537.36 |
| 命令行 | "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --disable-features=TabHoverCards --enable-audio-service-sandbox --enable-features=ParallelDownloading --flag-switches-begin --enable-quic --flag-switches-end --enable-audio-service-sandbox |
| 可执行文件路径 | C:\Program Files (x86)\Google\Chrome\Application\chrome.exe |
| 个人资料路径 | C:\Users\wlei3\AppData\Local\Google\Chrome\User Data\Default |
| 其他变体 | af81735d-ca7d8d80dff70c3e-ca7d8d80317c6f31-377be55a |
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure at the raw GitHub README URL and inspect the console error for pages/help_dialog.html. Trace which Vimium function handles the T key there and identify the relevant security-policy context; done means that function responds on the reproduced page without the sandbox error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100