Issue metadata
Sign in to add a comment
|
Inputs are disabled in offline mode
Reported by
wormssm...@gmail.com,
Dec 1 2017
|
||||||||||||||||||||||
Issue descriptionExample URL: https://wormss.net/sabertooth-pinout Steps to reproduce the problem: 1. Go to a url that has inputs. (https://wormss.net/sabertooth-pinout) 2. Then go offline 3. Open chrome again - notice you are in offline mode. 4. Observe that inputs are now disabled. What is the expected behavior? Inputs should not be disabled. I have local javascript detects changes to these inputs and that sets some dataset to some attributes that css alters the view. There are no external calls to other resources. What went wrong? All inputs are disabled by the browser, I have no code to enable/disable these inputs, so it is ALL browser side. Does it occur on multiple sites: N/A Is it a problem with a plugin? No Did this work before? Yes - Does this work in other browsers? N/A Chrome version: 62.0.3202.84 Channel: stable OS Version: 8.0.0, Nexus 5X Build/OPR6.170623.023 Flash Version: - I have come across a second person who is having this issue on StackOverflow. They imply it used to work, but now does not, I am unsure what version it used to work in. https://stackoverflow.com/questions/43304550/form-disabled-when-offline-using-html5-app-cache
,
Dec 4 2017
Tested the issue in Android and could reproduce the issue. Observed the input fields are seen disabled. Steps Followed: 1. Launched Chrome Browser. 2. Navigated to https://wormss.net/sabertooth-pinout 3. Able to click on input fields 4. Closed browser and went offline 5. Re-launched browser and Observed the input fields are seen disabled. Chrome versions tested: 62.0.3202.84, 64.0.3282.0 OS Android 8.0.0 Android Devices 8.0.0; Pixel XL Build/OPR1.170623.027 Below is the bisect info ======================= Chrome Good Build -- 59.0.3050.0 Chrome Bad Build -- 59.0.3051.1 Manual CL: https://chromium.googlesource.com/chromium/src/+log/59.0.3050.0..59.0.3051.0?pretty=fuller&n=10000 Unable to provide the tool bisect info as getting all good builds in bisect. From the above revision range suspecting the following change have fixed the issue and assigning the issue to the owner concerned-- https://chromium.googlesource.com/chromium/src/+/b382956014fb295322ee15b14f72712b93b174aa @fgorski -- Could you please look into the issue and help us in assigning this issue to the appropriate owner. Please navigate to below link for log's and video-- go/chrome-androidlogs/790942 Thanks!!
,
Dec 4 2017
This works as intended. At present our offline format does not include JavaScript and only provides static snapshots. We also disable form input. We'll look at this in triage on Wednesday to see if we can do anything for this case. If this is a sort of interactive application in JS, perhaps switching to Service Worker would be a way to provide offline functionality in this case.
,
Dec 5 2017
,
Dec 6 2017
#3 is correct, while offline it's close to impossible to make arbitrary Web page to function correctly. So for offline, Chrome 'degrades' the experience to the static snapshot of the DOM. This is still readable but not interactive. We do this for regular pages that were not designed to gracefully behave while offline. The way to build a Web App that works offline is to deliberately implement this functionality using Service Worker (this makes the app to be a PWA, Progressive Web App). These can run JS while offline. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by pnangunoori@chromium.org
, Dec 4 2017