A Chrome/Edge extension that automatically refreshes tabs on a schedule and by exact URL while protecting data being entered on the page.
- Configure intervals from 1 second to 24 hours.
- Store multiple exact URLs in one rule and share the same interval across them.
- Add each URL on its own row with the
+button and remove it independently. - Automatically pause when the current URL does not match, then resume when a configured URL opens again.
- Detect
input,textarea,select,contenteditable, and elements withrole="textbox". - Pause while typing or while unsaved form data exists.
- Configure automatic resume after a custom inactivity period; the default is 30 seconds.
- Manage each tab independently and restore schedules after the browser restarts.
- Request website access only when a refresh rule is created for that website.
- Always bypass the page cache when refreshing without clearing cache for other websites.
- Use a fallback alarm for intervals below 30 seconds to prevent a throttled page timer from becoming stuck.
- Show the remaining time on the extension badge, such as
20s,19s, and18s. - Continue counting and refreshing when the user switches to another tab.
- Keep URL rules after a tab closes and automatically start again when a matching URL is reopened.
- Use the fixed unpacked extension ID
npbemfdajjnhnjgmbagbhebbeooolpdcthrough the configured public key.
- Open
chrome://extensionsin Chrome oredge://extensionsin Edge. - Enable Developer mode.
- Select Load unpacked.
- Choose this project directory.
- Open a website, select the extension icon, and create a refresh schedule.
- Intervals below 30 seconds use a page timer and can be delayed when the browser throttles, freezes, or discards a background tab.
- The extension cannot run on browser system pages such as
chrome://andedge://. - A submit event does not prove that every website saved a form successfully, so input protection remains conservative.
- Input inside a cross-origin iframe can only be monitored when the extension has permission for that iframe origin. The current release monitors the main frame.
- The manifest
keycontains a public key, not a private key or secret.
npm test
npm run check
The repository remote is:
https://github.com/okebaybii/AutoRefresh-Page.git
- The earlier
git adderror (.git/index.lock: Permission denied) was caused by the local sandbox blocking writes to.git. It was resolved by granting repository-write permission, and both local commits now exist successfully. - Git has a host-specific proxy configured:
http.https://github.com.proxy=http://proxy.hcm.fpt.vn:80. proxy.hcm.fpt.vnresolves to42.113.52.189and42.113.52.190, but TCP port80times out.- A direct connection to
github.com:443also times out. - The SSH-over-HTTPS endpoint
ssh.github.com:443also times out. - The local commit is valid; the failure occurs before GitHub authentication or repository authorization.
This means the corporate proxy or firewall is blocking the connection. Changing Git credentials will not fix this network-level failure.
Ask the network administrator to allow these destinations:
| Purpose | Destination |
|---|---|
| HTTPS Git fetch/push | github.com on TCP port 443 |
| Exact repository URL prefix | https://github.com/okebaybii/AutoRefresh-Page.git |
| Optional SSH over HTTPS | ssh.github.com on TCP port 443 |
| Optional GitHub CLI/API | api.github.com on TCP port 443 |
| Optional browser authentication | https://github.com/login/* |
Allowlisting by hostname is preferred because GitHub IP ranges can change. GitHub's official restricted-network guidance is available at:
- Troubleshooting connectivity problems
- Allowing access from a restricted network
- Using SSH over the HTTPS port
After IT restores access to proxy.hcm.fpt.vn:80, use:
git push -u origin mainIf the current network permits direct GitHub access, bypass the host-specific Git proxy for one command:
git -c http.https://github.com.proxy= push -u origin mainThis command does not modify the global Git configuration. It will not work while direct access to github.com:443 remains blocked.
If ssh.github.com:443 is allowlisted and an SSH key is registered with GitHub, test the connection:
ssh -T -p 443 git@ssh.github.comThen use this remote URL:
ssh://git@ssh.github.com:443/okebaybii/AutoRefresh-Page.git
Do not switch the repository remote to this URL until the SSH test succeeds.