Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upSupport reloads that don't fetch from the cache #26411
Open
Labels
Projects
Milestone
Comments
|
Watching someone do a livestream and try to develop, this is a huge productivity killer. We need to add this ASAP. |
|
For the purposes of the next release, I think we should make the refresh button clear the cache. |
bors-servo
added a commit
that referenced
this issue
Jul 28, 2020
Make reload button clear the network cache. The developer workflow in FxR is frustrating right now because of bugs like #24385. To allow us to put out a new release soon that addresses this papercut, these changes make the reload button clear the network cache in FxR. --- - [x] `./mach build -d` does not report any errors - [x] `./mach test-tidy` does not report any errors - [x] These changes fix (kind of) #26411. - [x] These changes do not require tests because can't test FxR.
bors-servo
added a commit
that referenced
this issue
Jul 28, 2020
Make reload button clear the network cache. The developer workflow in FxR is frustrating right now because of bugs like #24385. To allow us to put out a new release soon that addresses this papercut, these changes make the reload button clear the network cache in FxR. --- - [x] `./mach build -d` does not report any errors - [x] `./mach test-tidy` does not report any errors - [x] These changes fix (kind of) #26411. - [x] These changes do not require tests because can't test FxR.
bors-servo
added a commit
that referenced
this issue
Jul 28, 2020
Make reload button clear the network cache. The developer workflow in FxR is frustrating right now because of bugs like #24385. To allow us to put out a new release soon that addresses this papercut, these changes make the reload button clear the network cache in FxR. --- - [x] `./mach build -d` does not report any errors - [x] `./mach test-tidy` does not report any errors - [x] These changes fix (kind of) #26411. - [x] These changes do not require tests because can't test FxR.
bors-servo
added a commit
that referenced
this issue
Jul 28, 2020
Make reload button clear the network cache. The developer workflow in FxR is frustrating right now because of bugs like #24385. To allow us to put out a new release soon that addresses this papercut, these changes make the reload button clear the network cache in FxR. --- - [x] `./mach build -d` does not report any errors - [x] `./mach test-tidy` does not report any errors - [x] These changes fix (kind of) #26411. - [x] These changes do not require tests because can't test FxR.
bors-servo
added a commit
that referenced
this issue
Jul 28, 2020
Make reload button clear the network cache. The developer workflow in FxR is frustrating right now because of bugs like #24385. To allow us to put out a new release soon that addresses this papercut, these changes make the reload button clear the network cache in FxR. --- - [x] `./mach build -d` does not report any errors - [x] `./mach test-tidy` does not report any errors - [x] These changes fix (kind of) #26411. - [x] These changes do not require tests because can't test FxR.
bors-servo
added a commit
that referenced
this issue
Jul 28, 2020
Make reload button clear the network cache. The developer workflow in FxR is frustrating right now because of bugs like #24385. To allow us to put out a new release soon that addresses this papercut, these changes make the reload button clear the network cache in FxR. --- - [x] `./mach build -d` does not report any errors - [x] `./mach test-tidy` does not report any errors - [x] These changes fix (kind of) #26411. - [x] These changes do not require tests because can't test FxR.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
To support web developers who want to have a quick edit-reload development cycle, we need to ensure that any bugs in our network cache implementation do not block them. We should ensure that it is possible to opt-in to reloading a page and guarantee that no cached content will be used.
The quickest way to support this would be to add an embedding API for clearing the entire network cache, so the usual reload operation will Just Work for this purpose.