I'm currently using verison 72.0.3626.119 on a Debian Strecht. I've noticed that since a couple of days (perhaps one or two weeks)
I'm missing the Replay XHR menu entry you get when you do a right click on an XHR request in the network
window as described here.
I've been also searching google for this with mixed results, I've found this SO question from 2016 where
the OP seems to have a similar issue but since my xhr request are not uploading files, this does not apply to me either.
In the devtool forums I've found nothing that could help.
So the question is, is this function also gone for everybody else? Or is it just me? I've gone through the devtools
settings but I didn't find any option that would help me with this.
The replay XHR still there if you are using the xhr api via axios or something similar, however, if your app is using the new api fetch, you need to use a different approach.
Since Chrome 67, it was introduced a new feature called copy as fetch.
In that case, you can copy as fetch and paste on your console.
So, if you'd like to replay your fetch requests, just paste on your console, then press ↑ and enter to replay your XHR.
The best part of that on the new feature is that you are able to edit your request, before replay.
Related
I use remote debugging of devtool to debug a webpage in Android.
I have learnt that devtool first downloaded some file(filename screen capture) necessary to debug page of webview.
However, when i clicked the filter of Network tab, something strange happened.
For example, i click XHR filter with the expection of filtering only xhr request, but only to toggle other filters than XHR tab, like All, JS, CSS, Img...gif of bizarre behavior
I used remote debugging before, but didn't encounter this strange behavior.
Is this the problem about version? I can't control the version of file which is downloaded by devtool.
Is this an official problem? Please help me, thank in advance!
I am having problems with performing actions on the Dataprep dashboard. In particular, when I try to merge two datasets, its just loading there for >20 minutes without a result. I tried to also add a new receipe or dataset and I only get that it gets stuck at 99%.
What is wrong with Dataprep Dashboard?
While I can't provide a specific reference, I've found that this can happen when you have a bad cache entry in your browser (either from a recent update to Dataprep or something related to the Flow itself).
Our team has found that this can often be resolved, but you can test that theory by opening a new Incognito window in Chrome (or another browser altogether) and loading your recipe there. If the problem goes away, it's likely that it was a caching issue—so you can just clear your cache for the Dataprep domain. (This has the advantage of also isolating things like LocalStorage.)
If you don't want to have to log in to your account from another window, you can also try hard-refreshing the page (Windows/Linux: Ctrl+F5, Mac: ⌘ Cmd+Shift+R)—or opening the Chrome Dev Tools, switching to the Network panel, checking the "Disable cache" button, and reloading the page. The plus here is that it allows you to test the issue without breaking your ability to recreate it (like if you want to submit a bug report).
Best of luck!
I am building an extension for VS Code. My extension will show the key bindings associated to a recently action (I am a fan of this for helping me learn key bindings).
Looking through the documentation there seems to be a way to access the commands in the editor, but no way that I can find to listen for actions / commands as they are invoked.
Is this possible with the current API? Or should I create a feature request in Github?
This isn't possible with the current release 0.10.3. I opened an issue in Github and was told by one of the devs that its not possible right now. It is a feature request for future versions. If it becomes available I'll update it here.
My site eighttwentydesign is running Joomla 3.0. I have SEF URLs on, and have done for sometime without issue. But today when you go to the site, and click on anything, say portfolio you get the home page under the portfolio's URL, but if you add a leading slash at the end, the right article (portfolio) shows. Additionally, if you click on say "Web Design" it sends you to the Portfolio page. I might add this menu is a menu within Joomla - not be adding internal links manually
Doesn't work: http://www.eighttwentydesign.com/portfolio
Does work: http://www.eighttwentydesign.com/portfolio/
I have checked the .htaccess, and actually reverted it to the original with no luck, I have check Global Config but I can't see anything which may cause this. It was working nicely yesterday. I haven't adapted with any PHP source or anything in the past few weeks, the only notifiable thing I have done is yesterday enabling the Cache - have others experienced problems after doing this? I have disabled it under global config, with no avail.
Exact Joomla Version is 3.0.2 with very few plugins
I do have daily backups, but would rather a solution and be able to figure out a prevention from that, rather than just putting on a band aid.
I've search for a good couple of hours, and aside from just not being able to fix it, it appears no one else is experiencing this, so I am starting to think it may be a bug.
Just as I was about to post this I discovered my solution.
If you are having your SEF URLs display the wrong content then solve it by disabling the Cache plugin. You can do this by doing the following steps
Login to Joomla backend
Navigate to Extensions > Plugins
Go to "System Cache"
Disable system cache
I hope this helps someone in the future as I really struggled to find any answers on this.
I want to reload a plugin after update without restarting browser. I tried the mac version, it works fine, howeve, I need to change the plugin name for each version.
navigator.plugins.refresh(false);
http://www.firebreath.org/display/documentation/Deploying+and+updating+your+plugin?focusedCommentId=8585308#comment-8585308
In windows, I tried those steps and I couldn't make it work. Has anyone had any luck with this? Does anyone know what could be wrong?
"On Windows you even need to install it to a version-specific directory with a version-specific filename. Once the plugin is installed, you can try the following to reload the plugin in open browsers
<script>
var myplugin = "<object id=\"plugin\" type=\"application/x-foobar\"> </object>";
function onload(){ // Assuming this function put your plugin on the page in the first place
document.getElementById('pluginHere').innerHTML = myplugin;
}
function reload(){
document.getElementById('pluginHere').innerHTML = "";
document.getElementById('pluginHere').innerHTML = myplugin;
}
</script>
thanks alot.
This is a difficult trick that can go wrong in a lot of different ways. It's difficult for me to guess what might be going wrong specifically, particularly since you said "on windows", but you haven't specified what browser that is. All of the browsers work differently in subtle ways and IE and the others are completely different as far as this goes.
Things you could try:
use setTimeout to add a small delay between removing the plugin from the DOM and re-adding it
open about:plugins and then shift-refresh to see if it picks up the new version
Try different browsers and see what the behavior is
Use Process Monitor to monitor the queries of the registry and see when the registry keys are being accessed; use this to help plan your strategy.
Anyway, I hope some of that helps; I used to upgrade that way but it was too error prone and too prone to things changing with new browsers, so these days I just make the client restart their browser on upgrades. It saves a lot of hassle and lots of development time.
I use a signed CAB with MSI inside to load the plugin on internet explorer.
On the first time install I found that the plugin can be accessed from Javascript but events were not working.
When I looked at loaded plugins, the plugin was not loaded.
If I refreshed the page the plugin is loaded.
my solution was to add the following code from this stack overflow question
One time page refresh after first page load
This worked like a charm.