Firefox's shader editor can't always access or update shaders
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
On some web pages, the shader editor is endlessly waiting for a WebGL context while the program is actually running and displayed on screen.
I also notice that in some cases the shaders show up in the editor but when I want to edit one of them (a meaningless line return is enough for this to happen), the objects the shader is linked to disappear from the screen in the following frames.
Shaders from https://threejs.org/examples/ never show up in the shader editor panel, but shaders from http://webglsamples.org always do. I excluded a three.js fault because many pages using this library such as this one http://armsglobe.chromeexperiments.com are handled correctly.
I have reproduced the problem on windows and ubuntu with up to date versions of Firefox and Firefox Developer Edition as well as Google Chrome and Chromium (using this addon https://chrome.google.com/webstore/detail/shader-editor/ggeaidddejpbakgafapihjbgdlbbbpob).
Any idea what is happening and how to work around it?
developer-tools webgl
asked Jan 31 at 19:14
geoffreygeoffrey
337
add a comment |
On some web pages, the shader editor is endlessly waiting for a WebGL context while the program is actually running and displayed on screen.
I also notice that in some cases the shaders show up in the editor but when I want to edit one of them (a meaningless line return is enough for this to happen), the objects the shader is linked to disappear from the screen in the following frames.
Shaders from https://threejs.org/examples/ never show up in the shader editor panel, but shaders from http://webglsamples.org always do. I excluded a three.js fault because many pages using this library such as this one http://armsglobe.chromeexperiments.com are handled correctly.
I have reproduced the problem on windows and ubuntu with up to date versions of Firefox and Firefox Developer Edition as well as Google Chrome and Chromium (using this addon https://chrome.google.com/webstore/detail/shader-editor/ggeaidddejpbakgafapihjbgdlbbbpob).
Any idea what is happening and how to work around it?
developer-tools webgl
asked Jan 31 at 19:14
geoffreygeoffrey
337
add a comment |
On some web pages, the shader editor is endlessly waiting for a WebGL context while the program is actually running and displayed on screen.
I also notice that in some cases the shaders show up in the editor but when I want to edit one of them (a meaningless line return is enough for this to happen), the objects the shader is linked to disappear from the screen in the following frames.
Shaders from https://threejs.org/examples/ never show up in the shader editor panel, but shaders from http://webglsamples.org always do. I excluded a three.js fault because many pages using this library such as this one http://armsglobe.chromeexperiments.com are handled correctly.
I have reproduced the problem on windows and ubuntu with up to date versions of Firefox and Firefox Developer Edition as well as Google Chrome and Chromium (using this addon https://chrome.google.com/webstore/detail/shader-editor/ggeaidddejpbakgafapihjbgdlbbbpob).
Any idea what is happening and how to work around it?
developer-tools webgl
asked Jan 31 at 19:14
geoffreygeoffrey
337
On some web pages, the shader editor is endlessly waiting for a WebGL context while the program is actually running and displayed on screen.
I also notice that in some cases the shaders show up in the editor but when I want to edit one of them (a meaningless line return is enough for this to happen), the objects the shader is linked to disappear from the screen in the following frames.
Shaders from https://threejs.org/examples/ never show up in the shader editor panel, but shaders from http://webglsamples.org always do. I excluded a three.js fault because many pages using this library such as this one http://armsglobe.chromeexperiments.com are handled correctly.
I have reproduced the problem on windows and ubuntu with up to date versions of Firefox and Firefox Developer Edition as well as Google Chrome and Chromium (using this addon https://chrome.google.com/webstore/detail/shader-editor/ggeaidddejpbakgafapihjbgdlbbbpob).
Any idea what is happening and how to work around it?
developer-tools webgl
developer-tools webgl
asked Jan 31 at 19:14
geoffreygeoffrey
337
asked Jan 31 at 19:14
geoffreygeoffrey
337
asked Jan 31 at 19:14
geoffreygeoffrey
337
asked Jan 31 at 19:14
geoffreygeoffrey
337
asked Jan 31 at 19:14
geoffreygeoffrey
337
337
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1400719%2ffirefoxs-shader-editor-cant-always-access-or-update-shaders%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1400719%2ffirefoxs-shader-editor-cant-always-access-or-update-shaders%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
