I'm getting the following error when I view my component in IE11 after loading webcomponents-loader.js. I tried upgrading to use the latest psk, as suggested elsewhere but that didn't seem to resolve the issue. Any ideas??
Which version of webcomponentsjs are u using?
there have been some "unstable" releases... I also similar errors on 1.0.5 and 1.0.6 if I remember correctly.
You could try 1.0.7 it was just release 3 days ago or go back to an earlier release.
Are you importing native-shim.js? If I remember correctly I had to import that to get IE to work correctly. (Well, mostly correctly, still fighting other issues.)
Related
I upgraded my angular project from 2 to 13 version and after that multiple tabs are not working properlyenter image description here
In order to help you, we may need more information. But, from my experience, this is probably a problem with a deprecated package that doesnt work with newest angular versions. So, while upgrading to newer major angular versions:
Skipping major versions is not recommended.
You have to upgrade all third-party dependecies in your package.json to support the angular version that you are using. In order to do this, you should go to each corresponding library's documentation and read information about version compatibility.
Visit https://update.angular.io for more detailed information.
So I've just got started with polymer and got this message:
[Deprecation] Styling master document from stylesheets defined in HTML Imports
is deprecated, and is planned to be removed in M65, around March 2018. Please
refer to ....... for possible migration paths.
After doing some reading it seems to be that
<link rel="import" href="/SOR/bower_components/paper-input/paper-input.html">
Was causing the issue and rel=import for html was being deprecated. Is this right? If so what is the fix, how should I be doing this?
Cheers
So, according to the new version of chrome (61.xx.x). Google has made a decision that Styling master document from stylesheets defined in HTML Imports
is not a good approach and so it will be unable to do in future chrome versions.
Because of this, we have to upgrade to version 2.x
Well, nothing much interesting except that Google has made a decision that HTML imports will be removed in future. This is much more frustrating. Everyone who is using Polymer 1.x or 2.x will have to update their projects to newer version of polymer (at least 3.x). Unfortunately version 3.x has no support in all major browsers (except Chrome, but not fully). So we can only hope that the remove of HTML imports will not be soon.
For me this is really piece of s**t. I have many projects written in Polymer and I am not able to upgrade them. (there is no time for this) even i had time, I don't have trust in Google Polymer... Their support is 0. They don't even answer to bugs. Old versions are already stopped from updating. No long-term support versions.
official discussion: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/VZraFwqnp9Y/discussion
The issue has actually been solved by the polymer team, as described on their blog
So versions 1.10.1 or newer for 1.x and 2.1.1 or newer for 2.x are ok, however the warning doesn't go away (see blog entry for more details).
I also tested a polymer 2.6 app on Chromium 65 and on chrome 67 beta and it works fine everywhere :)
If you are using Google Polymer it's worth remembering that webcomponents.js is actually a polyfill. We currently run Polymer version 0.5 and this can actually be tested by starting your current Chrome with those features disabled. On Mac you can do this quitting Chrome and then run from command line:
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --disable-blink-features=ShadowDOMV0,CustomElementsV0,HTMLImports
Polymer 0.5 applies the Polyfill when these features are disabled.
Here is the documentation on running Chrome in debug mode Chromium debug flags
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.
1)I just downloaded php storm EAP 7 and try implementing live Edit but it doesn't work. The error produced is " incompatible with this installation".
This is going to be kind of a no-answer:
I've had multiple issues with Live Edit and finally got the suggestion from the JetBrains support that I should turn it off because it interferes with the normal working of other componets. That being said, this was a few months ago, maybe the situation changed in the mean time.
I would suggest contacting their support, even if you don't have an (active) subscription, they tend to be very fast and helpful.
It works with the most current EAP Build.
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.