I am doing a POC in PWA and service worker, i hosted to application in localhost and tested in Chrome everything seems to working fine even the indexed db is getting listed properly.
to test the offline functionality :
in Inspector > Network Tab > Offline ( check the option )
When am in Edge i didn't see this option so tried disconnecting the network but still because it reading from localhost everything is working directly and reading from server.
To check the Indexeddb and all i installed the MS Edge DevTools preview, still am not able to see the DB and Store
Is there any way to test this in Edge
At present, Offline mode is not available in MS Edge.
If you want to see index db then you can open the developer tools and go to the debugger tab.
It looks like below.
You also not need to install developer tools additionally because by default it comes with Edge. You can directly use it.
You can try to check on your side. Let us know if you still have problem in finding the index db in Edge, We will try to provide further suggestions.
Related
I'm experiencing the combination of a locally installed Microsoft Edge Chromium Enterprise Edition and Microsoft App-V. I try to App-V a browser plugin for a locally installed Microsoft Edge Chrome Enterprise.
I have an App-V bubble and Internet Explorer is started with this bubble in the background using the /appvve command-line option.
My first suggestion was:
Replace the file path to iexplore.exe to the new file path of msedge.exe, eg.
"C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe" --site-per-process -url https://www.website.com /appvve:[App-V PackageID]_[App-V PackageVersionID]
This works only when MS Edge has no running instances already.
The --site-per-process option should help isolate the process of Edge Chromium.
When Microsoft Edge is already opened, there is some magic: the bubble is active for some seconds and after that the App-V bubble is closed.
ProcessExplorer of SysInternals does a great work: it tells me a secondary process of Edge Chromium is started with the bubble on the background.
Then the subprocesses of the secundary started instance are brought to the primaraly started instance and when this all is done, the secondary started instance - including the App-V bubble - is closed.
The webpage is opened, but the connection to the App-V bubble is lost.
The same happens when MS Edge-with-app-v is running bubble-a and you want start a secondary instance with bubble-b.
Could anyone tell me how to tell MS Edge to really isolate its processes and how it could work with multiple loaded App-V bubbles?
The only way I have successfully got around this is with the --no-sandbox, --app, and --user-data-dir switches.
For example:
C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe" --no-sandbox --user-data-dir"%LOCALAPPDATA%\Microsoft\Edge\AppV --app="https://www.website.com" /appvve:[App-V PackageID]_[App-V PackageVersionID]
This opens up the page in an App window and uses its own directory so the process isn't merged with existing or new instances of Edge that launch in the default directory.
I found this kept crashing until --no-sandbox was introduced. however, I'm a little on edge as the Sandbox helps keeps this secure. I'm also wondering how the Sandbox is interfering with App-V.
This is a workaround, but I do think MS will need to investigate this further as clearly the --site-per-process isn't separating each tab, at least not how we would expect.
While I have not tried to virtualize this under App-V, I am aware that others have done so, for example NickIT.
Off hand, I would guess that RunVirtual is what you are looking for.
We tried to load scripts but something went wrong.
Please make sure that your network settings allow you to download scripts from the following domain:
https://aid-frontend.prod.atl-paas.net/atlassian-id/front-end/4.5.0
Tried Google Chrome, Firefox, Internet explorer also tried with different PC.
Not able to login into bitbucket
I'm using Chrome Version 77.0.3865.120 (Official Build) (64-bit). I got the same error trying to log in to my group's Atlassian site, and I was able to fix it by specifically allowing JavaScript from Atlassian:
Open Chrome settings
Click on Advanced
Click on Privacy and Security
Click on Site Settings
Click on JavaScript
Make sure JavaScript is set to allowed
Next to Allow, click Add
Paste the URL from the error message in and click Add
I've faced a similar problem recently while traveling and trying to work from a new location.
First I've tried the steps from the previous answer which unfortunately didn't help me (but they definitely may be useful in a different case scenario).
I'm renting a house with an existing pre-configured WIFI router which I could get an access to manage it over the web UI.
I'm not sure which of the following helped me. I did the following changes to the router configuration:
Added the 8.8.8.8 as a primary DNS Server
Enabled IPV6
Disabled the built-in firewall (this one is the more likely one which fixed the issue)
I am building a static app with PouchDB on Google AppEngine.
When I open the site in a browser window, it is showing a version I uploaded several hours ago.
If I open the site in an incognito window, the updated version is displayed (therefore I don't think it is actually an error in the console).
I put a new version number in app.yaml
I have migrated all traffic to the new version.
I have cleared my cache, deleted cookies, checked my application data, everything. I even reinstalled Chrome and Firefox.
I updated my Python version and my Google AppEngine Launcher yesterday; the problem pre-dated that update.
Also: just discovered that if I go to the URL of the updated version
http://4.[app-id].appspot.com, it displays the correct, updated version.
This is happening in Chrome, Firefox, and Edge.
Edit: probably should have mentioned that my site uses Service Workers and IndexedDB. I assume my service workers are caching the previous version, but I would have thought that Ctrl + F5 would clear the cache and show the new version.
I think it must be the Service Workers caching the pages (which is, after all, what they are supposed to do). This is actually really annoying when you are developing though.
A guy called Rich Harris has documented this behaviour and some workarounds on a Github Gist.
Reloading the page doesn't behave as you'd expect
If you make a change to your service worker, then reloading the page
won't kill the old one and activate the new one (it detects the change
by requesting the service worker file each time and comparing the old
and the new byte-for-byte), leaving you somewhat confused as to why
your changes haven't taken effect. This is because the old window is
never actually closed, meaning there's never a time to swap them out –
you need to kill the tab completely then reopen it.
Or you can have the browser do that for you by going to the
Application tab in devtools (in Canary, not stable Chrome yet), going
to the Service Workers section, and checking 'Update on reload'.
UPDATE (13 Nov 2017): This functionality is now available in Chrome, so you don't even need to download Canary.
And here's which bits of the application cache to clear:
Probably a dumb question:
Right now, to see changes made in development, I run rails s and see the changes on the local version of my site. To see how changes look on my phone, I currently commit to Git (no matter how small the changes) and then push to heroku. This takes some time and results in lots of commits and deployments for minor changes (i.e. CSS stuff).
What is a more efficient way to test changes for rails web apps on mobile?
NOTE: I am aware I can shrink my browser but it never fails I get different outcomes on my phone.
Any help is appreciated.
RELATED: how do i run a development rails app / website on an ipod
You can also use Nitrous.io which is a cloud development environment. I like it because not only can I view my work on mobile, but since it's a hosted URL, I can share it with others while my server is running.
1) connect your phone to the same network that your local server is running on and point it to http://[your server's ip]:3000
2) use the XCode iOS Simulator and/or the Android Emulator
you can also use ngrok
https://ngrok.com/
which gives you a way to make an external tunnel to the outside world (for free) so you can use it outside of your local network
I am fairly new to ASP, so if anything doesn't make sense, or you think, "WHY WOULD YOU DO THAT?", it's becasue I really didn't know.
So the issue is that I created a Website using Visual Studio 2012 Express for Web. It was an ASP.NET MVC. I have spent over a week, working on this, doing testing and getting everything to work and look correctly. So I started the process of deploying it. I followed a couple guides, and felt like I did everything correctly.
Right now I am only trying to test my website on , and my first screen shows up. This screen is a "login" screen of sorts and is supposed to connect to my Access Database to check to see if a user should be admited to the next screen. But clicking the "Submit" button doesn't even open the Database. All of this works fine when I run it in Visual Studio.
What can I do to get this working?
Some steps I have tried and failed at:
-Redeploying
-Changing location of the Access DB
-I started to try to install configure and convert my Access Database to SQL Server, but I haven't been able to get that to work either.
If anyone has any suggestions, please let me know. If you need code examples or IIS settings, I will get them to you as fast as I can, but please help me because I don't want to have lost over a week of work.
Thanks,
D
Edit: After taking the suggestion from HansUp, it lead me to some other search terms that lead me to http://www.iis.net/learn/application-frameworks/running-classic-asp-applications-on-iis-7-and-iis-8/using-classic-asp-with-microsoft-access-databases-on-iis. I am using a 64-bit machine, and my application pool in IIS was not set to run 32-bit applicaions which when using Access ODBC drivers that are 32-bit casue a problem.
Set the IUSR account to Read/Write for the DB file and folder where the DB file is located.
Then, seeing as I was using a 64-bit machine, and the Access ODBC drivers that were being used were 32-bit, I had to set "Enable 32-bit Applications" to "true" in IIS, for the Application Pool that my site was using.
This is a link to where I found the 64-bit 32-bit solut
http://www.iis.net/learn/application-frameworks/running-classic-asp-applications-on-iis-7-and-iis-8/using-classic-asp-with-microsoft-access-databases-on-iis