I am developing my first extension for Chrome and as I am working on Ubuntu, I've encountered two awful bugs.
The first thing is that chrome.i18n.getUILanguage is not supported! (console gives me an error about unsupported method). The thing is that this problem is not listed on any WIKI page, which may become tricky for beginners. Anyone had similar issue? For now, I am using window.navigator.language.
The second bug is about rich notifications that are not supported (anyone knows when it will be released?). As far as I know, when the app will be about to send a notification, the scripts will stop due to the error (similar to the first bug). I am not sure if there is possibility to develop different packages for different platforms, but if I want my extension to be truly multi-platform, I will have to give up development of this feature.
Any suggestions or thoughts?
Thanks,
As i said earlier in a comment, it seems to be not supported with linux mint either where i'm developing the chrome extension.
In this link a member of the chrome team said that they submitted it... but this is not true.
Thanks for the window.navigator.language alternative.
Related
I have been doing a research for quite a sometime but unable to find a good solution - therefore thought of asking on StackOverflow.
I have automated the testing using Selenium Webdriver for different browser but lately I had seen there were some issues which came for Chrome's older version - now, the question I had was if there is any way through which I could run the script for different versions of browsers e.g. test should run on Chrome 48 - Chrome 59 (covering majors versions only).
The two solution I got from my research was -
1.
Overriding the chrome binary location like the below link:
https://stackoverflow.com/a/16562068/6738995
I then started my research on how to download the binaries for Chrome and I found the official repo also - http://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html
2. Use Selenium Webdriver on cloud solution provider like BrowserStack or SauceLabs etc who provides multi-version-browser support
Now, I want to exhaust all the options related to the 1st approach i.e. if there is no proper/easy way to implement the solution then I would have go for the 2nd approach.
The reason I am reluctant to go for 2nd approach is that I might loose control(I am speculating that there might be some restrictions on using that platform, I might be wrong and could only find out the try after tring that) and also there will be learning curve associated with this and I would also have to spend time & resources in order to stabilize with the chosen technology.
Thanks in advance.
If resource isn't a concern/constraint for you, then you can use a Virtual Machine, like VMWare and simulate separate test environments with different web browsers. However, if you are looking for the best solution, then you have to use Cloud solutions like SauceLabs or BrowserStack.
We are looking for an easy way for our users to download and install a small client widget (it is a windows app) used with our (much larger) web app.
Our web app is currently only supported in Chrome.
Our concern is that the clickonce support piece may be missing from most Chrome installs.
The questions:
-- Is clickonce really going to be useful in this situation?
-- What is the best option for "one click" download-and-install for Chrome on windows?
ClickOnce uses NPAPI which is being removed from Chrome. You will need to look at NaCl, Native Messaging or PPAPI instead of ClickOnce. There used to be browser extensions that you could use, however they have been removed from the store (or no longer work).
Using Chrome should not matter, so yes Click once will be useful in this situation.
The only thing you need to worry about is your clients using Windows and the appropriate version of the .net framework. I hope this helps.
I've picked up the discover meteor ebook earlier today and have been following the steps. It's been a great experience and I hope I can contribute to this community once I have a more thorough understanding of the technology. All is going well and I was using firefox as my browser. I decided to install chrome since that is the browser I use on my host machine on a day to day basis. However when I load the project up in chrome its a blank screen. The console reports the following(pastebin)
http://pastebin.com/wvEaVNPv
Has anyone else experienced this issue?
YES! It comes and goes with time or development, and you will get different results in different browsers (ubuntu). I currently am getting
Uncaught ReferenceError: Package is not defined meteor.js:21
Uncaught ReferenceError: Package is not defined standard-app-packages.js:21
Uncaught ReferenceError: Package is not defined random.js:21
etc
A few weeks ago, chrome canary was bad but release chrome not. It may be some subtle code issue triggers things because as I developed madly but checked intermittently that problem came and went maybe three times, and once another browser gave me a clue on something it didn't like, which also cured chrome.
I don't have any tools/concepts to debug this further. I initially got through Discover Meteor using chrome about 2 months ago.
Check your accounts-ui-bootstrap-dropdown. If you are using bootstrap-3 you'll need accounts-ui-bootstrap-3. I found this as one possible cause when I went back.
I have a web server running Windows Server R2 Standard, and am experiencing the issue described in this blog post: http://www.hanselman.com/blog/BugAndFixASPNETFailsToDetectIE10CausingDoPostBackIsUndefinedJavaScriptErrorOrMaintainFF5ScrollbarPosition.aspx
In short, .Net is failing to recognise IE10 and is treating it as a downlevel browser without javascript support - if I understand the issue correctly.
I tried the following popular solutions:
Installed both hotfixes for .Net 2 and 4.
Manually updated the browser definition files in the .Net framework config folder and ran aspnet_regbrowsers.exe.
Put the new browser definition files in the App_Browsers directory.
Finally I upgraded to .Net 4.5 which solved the issue for .Net 4 sites running on the server, however .Net 2 sites are still experiencing the issue.
Because this is a live web server it has a lot of windows updates that have not been installed. I thought maybe there was an update that would address the issue. So I've taken a look at the updates but none of the descriptions seem to address the issue, so I cannot justify installing them and potentially causing more problems.
Does anyone have any other solutions or possible reasons why this issue just won't go away?
I have the same problem, and I haven't been able to figure out why none of the fixes work. However, I did find a workaround that might work for you: Setting the Page.ClientTarget attribute to "uplevel" overrides .NET's browser capability detection. Have a look at http://msdn.microsoft.com/en-us/library/system.web.ui.page.clienttarget.aspx for more information.
Have come through many microsoft hot fixes, they were working in local environment, but in the live server there was no result.
Setting up Page.ClientTarget = "uplevel" (preferably in a header or footer page) has really solved the issue. I think this the best solution, as your .net application may not detect any other browser in future. But then we may have to wait and see, if this fix has any side effects.
Is this possible? I think I may have missed something obvious here. I have a live UI scripts app, and I need to fix a bug. The potential bugfix has to be tested on multiple browsers, so it actually has to be published, instead of just trying out the "current version". This means that it has to be published to a new URL.
Thanks.
it actually has to be published, instead of just trying out the "current version" ?
There is no reason why using different browsers should prevent from using de 'dev' version of an app... you can login in many browser at the same time and play with the dev version on each browser (I do that very often using a couple of android and osX browsers simultaneously). Did you try and did you meet issues doing so ?