You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Better XML declaration error reporting for non-existing element #501
For an error, where I have misused a component in the XML. I would expect to see path to the XML along with line and column in the XML, rather than the source in the component-builder.js where the error occured.
changed the title [-]Better XML declaration element error reporting[/-][+]Better XML declaration error reporting for non-existing element[/+]on Jul 30, 2015
Activity
[-]XML declaration error reporting[/-][+]Better XML declaration error reporting[/+][-]Better XML declaration error reporting[/-][+]Better XML declaration element error reporting[/+][-]Better XML declaration element error reporting[/-][+]Better XML declaration error reporting for non-existing element[/+]RobzInadE commentedon Aug 6, 2015
+1
Confused me too when i tried porting my Page.optionsBar to the new actionbar in my view xml
lock commentedon Aug 30, 2019
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.