[
https://issues.apache.org/jira/browse/CB-6161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13923435#comment-13923435
]
Patrick Mueller commented on CB-6161:
-------------------------------------
Wanna try something? Include the following function, and run it early on your
page. It may narrow the scope of the error checking weinre is doing, so that
you can see *some* of the styles. No idea if it will actually work or not
though.
Since it's also choking on the ng-cloak style bits, you could try removing any
refs you have to ng-cloak, but of course you might be actively using it (like I
do), which would be a problem.
I'm also afraid that even though I've only seen it throw on ng-cloak, I don't
know that the crazy styles Angular uses aren't similar to that, and it may
break on just about everything. Dunno.
{noformat}
function whackWebkitMatchesSelector() {
var oldMatches = Element.prototype.webkitMatchesSelector
function newMatches(selector) {
try {
return oldMatches.call(this, selector)
}
catch (err) {
return false
}
}
Element.prototype.webkitMatchesSelector = newMatches
}
whackWebkitMatchesSelector()
{noformat}
> [weinre] not working with angular-seed
> --------------------------------------
>
> Key: CB-6161
> URL: https://issues.apache.org/jira/browse/CB-6161
> Project: Apache Cordova
> Issue Type: Bug
> Components: weinre
> Reporter: Patrick Mueller
> Assignee: Patrick Mueller
>
> Run angular-seed demo with these directions:
> {noformat}
> git clone https://github.com/angular/angular-seed.git
> cd angular-seed
> npm install
> scripts/web-server.js
> {noformat}
> If you instrument the {{app/index.html}} file with weinre, and then view with
> weinre, you won't see any style information.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
