on Chrome developer tools
Uncaught (in promise) Error: There is no clipping info for given tab
at E._handleResponsePromise (commons.js:1)
at E._handleDispatchResponse (commons.js:1)
at E._handleMessage (commons.js:1)
at _listener (commons.js:1)
at EventImpl.dispatchToListener (VM250 extensions::event_bindings:403)
at Event.publicClassPrototype.(anonymous function) [as dispatchToListener] (extensions::utils:138:26)
at EventImpl.dispatch_ (VM250 extensions::event_bindings:387)
at EventImpl.dispatch (VM250 extensions::event_bindings:409)
at Event.publicClassPrototype.(anonymous function) [as dispatch] (extensions::utils:138:26)
at messageListener (VM257 extensions::messaging:240)
I have no idea what this error really is about.
also no result in Google... Does anyone have the same problem?
It's raised by Evernote Web Clipper
Disable this extension will make chrome get rid of this error.
Related
I have an old rails webapp that uses prototypeJS and scriptaculous. In Chrome 83, sometimes, the methodized functions don't get their definitions and nothing works, functions remain undefined. Couple of reloads again, it starts working.
For instance - $(...).build is not a function at this line.
this.calendar_div = $(parent).build('div', {className: "calendar_date_select"}, style);
And in the updateChanges of Ajax.Autocompleter of Scriptaculous
TypeError: element.getStyle is not a function
at isDisplayed (javascripts/prototype.js?1591714063:3595:29)
at klass._begin (javascripts/prototype.js?1591714063:3654:11)
at klass.width (javascripts/prototype.js?1591714063:3801:39)
at klass._compute (javascripts/prototype.js?1591714063:3724:57)
at klass.get (javascripts/prototype.js?1591714063:3647:36)
at klass.get (javascripts/prototype.js?1591714063:447:22)
at Function.clonePosition (javascripts/prototype.js?1591714063:4319:29)
at Object.clone (javascripts/prototype.js?1591714063:7459:20)
at Object.options.onShow (javascripts/controls.js?1594789433:68:20)
at klass.show (javascripts/controls.js?1594789433:95:71)
This is turning out to be a nightmare, since it blocks major important functions within the app. Any pointers/ideas on how I can immediately deal with this will be God-sent. Thank you for listening.
I've got an application that seems to work fine when I put all my elements inside a <dom-bind> element. When I remove that dom-bind (no longer needed), most of the elements carry on working, but paper-card stops and throws an error:
"Uncaught DOMException: Failed to construct 'CustomElement': The result must not have attributes"
The error is thrown from polymer/lib/legacy/lib/class.html if that helps. Anyone got any ideas?
I had the same error, and find out angular create an empty element (), then bind stuffs to it.
This fail according to spec:
4.13.2 Requirements for custom element constructors
The element must not gain any attributes or children
https://html.spec.whatwg.org/multipage/custom-elements.html#custom-element-conformance
I fix my problem by assigning in connectedCallback()
I have got few issues while trying to implement a sliding menu ('Facebook' like) in my windows phone 8 application.
When I added the following code in app.xaml, it shows following issues
<Application.RootVisual>
<library:SlideApplicationFrame Header="ManageIT"
Background="White">
<!--<library:SlideApplicationFrame.LeftContent>
<pages:LeftView />
</library:SlideApplicationFrame.LeftContent>-->
<!--<library:SlideApplicationFrame.RightContent>
<pages:RightView />
</library:SlideApplicationFrame.RightContent>-->
</library:SlideApplicationFrame>
</Application.RootVisual>
The exception is given below.
Error 1 Nested properties are not supported: Application.RootVisual.
Error 2 The attachable property 'RootVisual' was not found in type 'Application'.
Error 3 Unexpected PROPERTYELEMENT in parse rule PropertyElement ::= . PROPERTYELEMENT Content? ENDTAG..
Can anyone help me to solve this?
Is it because the reference to System.Windows.UIElement is not done?
Update 1
I have undone the above change and add the following in mainpage.xaml after installing slideview using package manager console
Install-Package SlideView
Here is the code...
<controls:SlideView>
<Grid Background="Teal"
Width="400" />
<Grid Background="Tomato" />
<Grid Background="LightYellow" />
<Grid Background="YellowGreen"
Width="400"/>
</controls:SlideView>
But I have another set of build errors as follows...
Error 1 The namespace prefix "controls" is not defined.
Error 2 SlideView is not supported in a Silverlight project.
Error 3 The namespace prefix "controls" is not defined.
Error 4 The
type 'controls:SlideView' was not found. Verify that you are not
missing an assembly reference and that all referenced assemblies have
been built.
Update 2
Got the above issue fixed, but I have some run time exceptions as following...
System.InvalidOperationException was unhandled by user code
HResult=-2146233079
Message=Operation is not valid due to the current state of the object.
Source=Microsoft.Phone
StackTrace:
at Microsoft.Phone.Controls.PhoneApplicationFrame..ctor()
at slidingmenu.App.InitializePhoneApplication()
at slidingmenu.App..ctor()
InnerException:
Regards
Sebastian
Try to nest your controls in parent control such as StackPanel. Most likely you have messed up the namespaces. What i would do? It will be to compare my code with a working one. CodePlex provides an example source for SlideView. Download it and see what are you missing.
Is the xml namespace defined?
xmlns:controls="clr-namespace:SlideView.Library;assembly=SlideView.Library"
xmlns:slideview3="clr-namespace:slideview3"
If LeftView is one of your controls.
<library:SlideApplicationFrame.LeftContent>
<slideview3:LeftView />
</library:SlideApplicationFrame.LeftContent>
I had the same issue in my (MvvmCross-) app.
I was able to resolve this by creating the RootFrame by code in App.xaml.cs instead of adding it in the Xaml:
private void InitializePhoneApplication()
{
var slideApplicationFrame = new SlideApplicationFrame
{
LeftContent = new LeftView(),
RightContent = new RightView()
};
this.RootFrame = slideApplicationFrame;
this.RootVisual = this.RootFrame;
this.RootFrame.Navigated += this.CompleteInitializePhoneApplication;
// Handle navigation failures
this.RootFrame.NavigationFailed += this.RootFrameNavigationFailed;
}
...and removed the whole <Application.RootVisual>...</Application.RootVisual> in App.xaml.
I am using this everything works quite well, except :
When I click on link button, I get the following errors
Uncaught TypeError: Cannot read property 'text' of null _wysihtml5-0.3.0.js?body=1:6936
_format _wysihtml5-0.3.0.js?body=1:6936
wysihtml5.commands.createLink.exec _wysihtml5-0.3.0.js?body=1:6970
wysihtml5.Commands.Base.extend.exec _wysihtml5-0.3.0.js?body=1:6793
wysihtml5.toolbar.Toolbar.Base.extend._execCommand _wysihtml5-0.3.0.js?body=1:9180
wysihtml5.toolbar.Toolbar.Base.extend.execCommand _wysihtml5-0.3.0.js?body=1:9172
(anonymous function) _wysihtml5-0.3.0.js?body=1:9221
(anonymous function)
Any idea how I can fix this?
Thanks before for everyone's help :-)
it works with me.
you must include all required css and js file ( including http://jhollingworth.github.io/bootstrap-wysihtml5/lib/js/wysihtml5-0.3.0.js)
i updated a fiddle for your reference
please visit http://jsfiddle.net/suhailvs/vNPAJ/
I had a very similar issue, and found that the problem was because the create link dialog div element was not enclosed in the toolbar div.
I keep getting errors doing this:
puts browser.table(:after? => span(:text => "Asmeniniai duomenys") )[2][2].text
basically saying:
undefined method `span' for main:Object (NoMethodError)
or
undefined method `table' for main:Object (NoMethodError) etc...
so I decided that the table was not found. I tried if/else, but it's the first time I used ruby, I did not understand if it worked or not.
So I thought that the simplest way would be to find out how to highlight something.
Could anyone suggest how can I highlight elements or how to fix this problem?
I assume you mean to highlight the element so you can determine if the right element is being found.
You can use the Element#flash method. This method will change the background of the element a couple of times, which should help you figure out what element was found.
For example:
browser.table.flash