As of sometime last week, when I connect to my device (Flame) from webIDE (nightly) the CSS panel in inspector is blank for all nodes, and the CSS editor tab is empty with just a spinner where the stylesheets should be. In the console I see: A coding exception was thrown and uncaught in a Task. Full message: TypeError: target.client.traits.customHighlighters.indexOf is not a function Full stack: exports.getHighlighterUtils/exported.hasCustomHighlighter@resource://gre/modules/commonjs/toolkit/loader.js -> resource:///modules/devtools/framework/toolbox-highlighter-utils.js:78:12 StyleEditorUI.prototype.initialize/<@resource://app/modules/devtools/StyleEditorUI.jsm:125:11 TaskImpl_run@resource://gre/modules/Task.jsm:314:40 Handler.prototype.process@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:870:23 this.PromiseWalker.walkerLoop@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:749:7 this.PromiseWalker.scheduleWalkerLoop/<@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:691:37 I tried about:app-manager and got the same error there FWIW. This however looks like a symptom not a cause. Not sure if the problem is unique to my machine/install somehow (Ubuntu 12.04) - it did all used to work. Today I've reinstalled nightly, and also deleted/recreated a fresh profile with no effect. The only event I can think of that might have precipitated this is I ran some UI tests on device (using adb forward tcp:2828 tcp:2828) and I don't think I've seen CSS on WebIDE since. All the other functionality works fine however, so that could be irrelevant.
Doubled checked my nightly version, about:support says: Name: Firefox Version: 38.0a1 User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:38.0) Gecko/20100101 Firefox/38.0 Multiprocess Windows: 2/2 Extensions ---------- Name: ADB Helper Version: 0.7.3 Enabled: true ID: firstname.lastname@example.org Name: Firefox Developer Tools Adapters Version: 0.2.4 Enabled: true ID: email@example.com Name: Ubuntu Firefox Modifications Version: 3.0 Enabled: true ID: firstname.lastname@example.org I flashed a Flame with 2.2 and confirmed everything works as expected there. Its just the other device on master/trunk which has the CSS issue. I'll try re-flashing that though to rule out it getting into a funky state somehow.
> Its just the other device on master/trunk which has the CSS issue. I'll try > re-flashing that though to rule out it getting into a funky state somehow. Reset that device completely and put mozilla-central back on there and I reproduced the issue again.
I got the same stack trace when I go to stylesheet pane, but I noticed in about:buildconfig: --host=x86_64-linux-gnu --prefix=/usr --libexecdir=/usr/lib/firefox-trunk '--with-l10n-base=/build/buildd/firefox-trunk-38.0~a1~hg20150116r224177/./l10n' '--srcdir=/build/buildd/firefox-trunk-38.0~a1~hg20150116r224177/.' --enable-release --disable-install-strip --disable-updater --enable-application=browser --enable-startup-notification --with-distribution-id=com.ubuntu --enable-optimize --enable-tests --disable-crashreporter --with-branding=browser/branding/nightly --disable-gnomevfs --enable-gio --enable-update-channel=nightly --disable-debug --disable-elf-hack --with-app-name=firefox-trunk --with-app-profile=.mozilla/firefox-trunk --enable-profiling '--with-google-api-keyfile=/build/buildd/firefox-trunk-38.0~a1~hg20150116r224177/debian/ga' '--with-google-oauth-api-keyfile=/build/buildd/firefox-trunk-38.0~a1~hg20150116r224177/debian/go' ...which suggests this build is actually from 2015-01-16, which is no-one's definition of "nightly". As https://hg.mozilla.org/mozilla-central/rev/2dc360586545 landed 2015-02-03, I'm going to assume this is the problem.
As discussed on IRC, the issue relates to the change in bug 1127238, which happens to force any trying to connect to a server / phone with 2015-02-03 or later to also be using a client from 2015-02-03 or later. I believe the DevTools team can do better in the future to avoid trouble like this, but it hasn't yet been an explicit compatibility goal to support a client that is older than the server. I'll close this for now, but if you still see an issue once you got desktop updated past 2015-02-03, please re-open!
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.