I tried to port my succesefuly worked my kendo-based site as chrome app. But app does not works. I found on chrome developer console exception message "extensions::platformApp:17 history.pushState is not available in packaged apps." on
<script src="kendo/js/kendo.mobile.min.js"></script> string
I found the same problem on angular with a solution, but did not found for the Kendo.
Any way to resolve it?
By default Kendo UI (and Mobile) doesn't use the History API, due to its rather limited support in the past. If you explicitly enabled it, you can delete this option, though you will probably have to update your navigation throughout the apps:
http://docs.telerik.com/kendo-ui/api/javascript/mobile/application#configuration-pushState
Related
Background
I've been using the crx-hotreload package to auto-reload my chrome extensions during development because it's annoying to have to click the refresh button on the Extensions page every time you make a change; however, this package doesn't work with MV3 because it uses the chrome.runtime.getPackageDirectoryEntry method, which seems to have been removed from chrome.runtime in MV3. I can't find documentation to confirm that it was removed, but it's not there when I try to use it.
Questions
Does anyone know how to get access to all the files in the extension directory in Chrome Extension Manifest Version 3?
Or generally, is there a better way that I can hot-reload my chrome extensions during development that would work for MV3?
This is one of many things based on DOM capabilities of background pages that are removed from ManifestV3 because service workers don't have DOM. For example, getPackageDirectoryEntry is using the old nonstandard FileSystem API in its returned value.
As to why, apparently the switch to service workers simplifies the internal source code in Chromium, even if it doesn't provide any real improvements for extension authors or users.
At this point all you can do is present a convincing use case and ask Chromium developers via https://crbug.com to implement an alternative API.
I am creating a web app which requires a login. It seems my webview autofill/autocomplete does not work. Is this feature disabled by default? In my search through the web I have found many posts asking how to disable this feature, leading me to believe that it is enabled by default. My credentials are remembered and autofilled fine when testing my web app in chrome for android. I have also loaded gmail in my webview and tested to see if autofill worked, and I still could not get it to work. My app is set for SDK 18 and up.
Thanks
I have created my first Chrome extension/app and found out that lightboxes do not function inside the app. I created the app from the Google example kiosk app. I'm only using webview in the app and have no other customizations. It just points to a link.
I want to use the app as an auto-launch Kiosk app on a Chromebox. Via this website I found that 'alert' and 'confirm' are a disabled web feature on chrome web apps.
I am wondering if it is possible to enable alert and confirm in the Chrome app so that lightboxes will work when interacting with a website.
Thanks in advance.
Yes you can definitely call alert box inside a chrome extension, just like you would in a normal javasript file as stated in this thread.
chrome.browserAction.onClicked.addListener(
alert("Im an alert box triggered by Chrome Extension")
);
The link you provided suggests that you can create a custom popup/lightbox as a workaround. There's a complete tutorial here.
Happy coding! :)
As Dart web application compiled to JavaScript required a quite recent browser, it could be useful to advise web user with an old browser that they need to upgrade it.
Whith this package http://pub.dartlang.org/packages/browser_detect you should get the browser make and version.
This way you can check if the user has an officially supported browser, or a browser you have tested your app with.
If this is not what you want then it depends on what features you use. Some features work in many browsers other only in the officially supported browsers (or should work).
For some features there is an attribute to check if it is supported by the browser, for others you would need a workaround or hack.
I would like to add the ability to cast my chrome packaged app to a google chromecast device.
So far google states that all you have to do is add
to your page and the API will inject itself.
For me that doesn't happen. No code is injected.
Am I doing something wrong?
There doesn't seem to be a demo showing this type of capability.
EDIT:
I just wanted to clarify a bit. All that I would like to do is display my app to a screen.
I have no media. I simply want to display it exactly as the chrome extension in the chrome browser would.Therefore I would follow the directions for a sender only. The app is packaged so it is running only CSS/JS/HTML5 code. The app is designed to run offline.
Steps I've taken to cast:
1. I've added the extra bit to the HTML line:
2. I've followed the whitelisting, to the best of my understanding, by adding my "website address" to the chrome extension. So I've added the only two address that should matter.
127.0.0.1
192.168.1.106
There is a good chance Content Security Policy is blocking the implementation of the cast API being injected. I see that you've filed Issue 287254: Google cast (chromecast) ability for packaged apps, and suspect we will need to wait for it to be implemented in a packaged apps compliant way.
You must whitelist your device and your Chrome app. See here for more details:
https://developers.google.com/cast/whitelisting#whitelist-chrome