Refresh n Click - Auto Click

Type the words on the button you are waiting for. Refresh n Click reloads the page until that button appears, clicks it, and stops. Waiting on more than one button? Add a step for each and it works through them in order — Add to cart, then Checkout, then Confirm. Useful when a page will not tell you it has changed: a seat opening up, a restock, a booking slot, a queue letting you through, a build finishing. WHAT IT DOES • Reloads the tab until text you specify shows up on the page • Clicks the matching button, link or control the moment it appears • Takes as many steps as you need, in the order you type them, each with its own text • Only the first step refreshes: once a click lands it watches the page the flow moved to, rather than reloading a cart or a checkout • Moves on only when the page actually reacts to a click — a click that changed nothing ends the run instead of pressing on • Stops by itself once the last step is clicked and does not keep going — unless you tick Loop • Reports how long each load took, in milliseconds, and how many times it has refreshed FINDING THE RIGHT THING TO CLICK Pages are messier than they look, so the search is deliberately thorough: • Match the text exactly, or match anything containing it — set per step, so a Checkout button carrying a basket count can be matched loosely while a short confirm word stays exact • Works on buttons, links, and anything else that is actually clickable — including elements a page has made clickable itself • Looks inside iframes, so buttons in embedded checkout and booking widgets are found rather than missed • Looks inside open shadow DOM, so modern web components are covered • Also matches on a control's accessible name, tooltip, image alt text, or input value — useful when a button shows only an icon • Ignores spacing: line breaks and indentation in the page source do not matter, and the ideographic spacing often used to pad short Chinese and Japanese labels is handled too, so "確定" matches a button that reads "確　定" And just as deliberately careful about what it will not click: • Hidden, fully transparent, disabled, or non-interactive elements are skipped. Pages often keep an invisible copy of a button in the markup — clicking that one would do nothing while looking like success • After clicking it checks whether the page reacted, and tells you when nothing did instead of reporting success • Not every page will act on it: a click made by a script is not a click made by a mouse, and some pages only accept the second. When that happens it says so instead of claiming success • Buttons that render late, or fade in, are waited for rather than missed TIMING • Fastest mode reloads as soon as the previous load has finished • Or set your own interval, anywhere from 100 milliseconds to 10 minutes GOING ROUND A PAGE'S OWN TABS Some pages keep what you want to watch behind their own tabs — a dashboard, a board, a status page. Tick Loop and the list starts again at the top instead of ending: each step is clicked, left on screen for the interval you set, then the next one, round and round until you press Stop. • Nothing is reloaded on the way round — it is the same page from the first click to the last, and the interval is simply how long each tab stays up • One step loops too: a single button, pressed again every interval • It still ends the moment something is wrong — a click the page ignores, or a step whose text never turns up, stops the run exactly as it would without looping IF A SITE SENDS YOU SOMEWHERE ELSE Chrome takes an extension's access to a page away the moment that page moves to a different site — a checkout handing off to a payment provider, a queue system passing you on. The run is not thrown away when that happens: it pauses, keeps its place in your list of steps, and the tab's mark turns amber. Click the toolbar icon and press “Allow this site” to carry on from where it stopped. If the page comes back to a site it can already reach, it picks up again on its own. A pause nobody answers ends the run after a few minutes rather than waiting for ever. THE CONTROLS POP OUT INTO A WINDOW Press Start and the controls lift off into a small window that stays open while the tab reloads — Start, Stop, the live count and a countdown to the next reload are always in view. The work runs in the background, so closing the window does not stop it, and an amber badge on the toolbar icon counts how many runs are going. Each running tab is also marked in the tab strip, grouped and labelled with the extension's name, so you can see which pages are working without opening anything — and the moment the click lands, that group turns green, so the tab that clicked stands out even with every window closed — while a site that starts returning errors (a 502, a Cloudflare error page) turns it red until a healthy page comes back, and amber means the run is waiting for you to allow a site it was sent to; a tab you have grouped yourself is left where it is. When a run stops its mark is removed; only the green one stays until you next open the popup on that tab, or close it. Reopen it any time from the icon. A keyboard shortcut for Stop can be assigned at chrome://extensions/shortcuts — paste that into the address bar, it is not on the extension's own Details page; nothing is bound by default, so it cannot clash with anything you already use. It can also be set to work globally, so a run can be stopped while another app is in front. PRIVACY • No analytics, no account, no tracking • No remote code — everything that runs ships inside the extension and is reviewed by the Chrome Web Store • Nothing is transmitted anywhere. Your settings stay in your browser • Page content is examined in your browser only, to find the button you asked for • The text you type is remembered between runs so you do not have to type it again — clear it from your browser at any time with the × inside the field Permissions are limited to what those …