Example URL: [Wayback/Archive] track.amazon.com/tracking/NL2017506177
Via: [Wayback/Archive] Amazon Shipping
Related: Read the rest of this entry »
Posted by jpluimers on 2024/11/21
Example URL: [Wayback/Archive] track.amazon.com/tracking/NL2017506177
Via: [Wayback/Archive] Amazon Shipping
Related: Read the rest of this entry »
Posted in Bookmarklet, Development, JavaScript/ECMAScript, Scripting, Software Development, Web Browsers | Leave a Comment »
Posted by jpluimers on 2024/11/05
Two stage bookmarklet idea (so if will be easier to create this in an agile fashion):
Hopefully these links will help me getting started:
Posted in Bookmarklet, Development, JavaScript/ECMAScript, Power User, Scripting, Software Development, Web Browsers, Web Development | Leave a Comment »
Posted by jpluimers on 2024/09/12
This is cool as it shows the page source not as it was first loaded, but from how it is currently rendered which includes all post-load modifications by any scripts: [Wayback/Archive] View DOM Source bookmarklet.
Via [Wayback/Archive] Martin Splitt on Twitter: “I made a bookmarklet to view the rendered source (aka the DOM) of a page. 👀 🚀 Works with Chrome, Firefox, Safari and possibly others, too. 🌈 Beautifies the code 🎨 Includes syntax highlighting 💻 Get the bookmarklet at 👉 experiments.geekonaut.de/view-dom-source 👈”
Posted in Bookmarklet, CSS, Development, HTML, HTML5, JavaScript/ECMAScript, Power User, Scripting, Software Development, Web Browsers, Web Development | Leave a Comment »
Posted by jpluimers on 2024/09/11
Cool video about the basics of [Wayback/Archive] 11.2: Bookmarklets – Programming with Text – YouTube
–jeroen
Posted in Bookmarklet, Development, JavaScript/ECMAScript, Power User, Scripting, Software Development, Web Browsers, Web Development | Leave a Comment »
Posted by jpluimers on 2024/09/10
There are quite a lot of cool responses to b0rk asking this a while back: [Wayback/Archive] 🔎Julia Evans🔍 on Twitter: “does anyone know of a good demo (blog post / video) of how to use a Javascript debugger in a browser to investigate a bug? I’ve used debuggers in C but never Javascript”
Archived just in case I need to do more web development stuff.
Posted in Chrome, Development, Firefox, JavaScript/ECMAScript, Power User, Scripting, Software Development, Web Browsers, Web Development | Leave a Comment »
Posted by jpluimers on 2024/08/27
I put the proper Bookmarklet wrapper around the functions from Bookmarklet for Archive.is to navivate to the canonical link (because especially Firefox needs them):
An immediately invoked function that returns no value or an expression preceded by the
voidoperator will prevent the browser from attempting to parse the result of the evaluation as a snippet of HTML markup:javascript:(function(){ //Statements returning a non-undefined type, e.g. assignments })();
It means they now have become these:
javascript:(function(){location=document.querySelector('link[rel="canonical"]')?.href})();
javascript:(function(){prompt("Anchor",document.querySelector('link[rel="canonical"]')?.href)})();
--jeroen
Posted in archive.is / archive.today, Archiving, Bookmarklet, Chrome, Development, Firefox, Internet, JavaScript/ECMAScript, Power User, Scripting, Software Development, Web Browsers | Leave a Comment »
Posted by jpluimers on 2024/08/11
Interesting take of which I was subconsciously aware for a while as well: [Wayback/Archive] Thom :linux: :kde: :systemd:: “My concerns about the future o…” – Exquisite.social
My concerns [www.osnews.com] about the future of Firefox keep becoming reality [www.osnews.com] and yet nobody who relies on Firefox – Canonical, Fedora, KDE, GNOME, etc. – seem to give a shit.
Y’all realise Mozilla is about to lose 80% of its revenue, right? And y’all do understand what this will mean for Firefox, right? Why aren’t you taking any steps or making any plans to prepare for what this will inevitably mean for the most important and crucial desktop Linux application?
I feel like Kassandra [en.wikipedia.org] over here.
It is not a Desktop Linux problem alone: it is a Firefox problem at heart which will also (and in much larger numbers) affect other platforms as it also means one less browser engine: the Gecko browser engine used by Firefox and other browsers highly depends on Mozilla funding.
Given the long lasting keyboard productivity problems in Firefox on MacOS and Windows (even without any extensions installed), I don’t think that my frequency of Firefox usage will increase beyond occasional use.
A few examples hampering power usage of Firefox:
Posted in Development, Firefox, Power User, Software Development, Web Browsers, Windows Development, xCode/Mac/iPad/iPhone/iOS/cocoa | Leave a Comment »
Posted by jpluimers on 2024/08/08
Last year I posted about Some JavaScript bookmarklets for WordPress published pages centered around navigation and IDs.
It depended on HighlanderComments to exist in order for getting its .connectURL which contains the canonical blog post URL (i.e. from https://wiert.me it obtains https://wiert.wordpress.com).
Nowadays HighlanderComments does not always exist, but in that case <link rel="EditURI" type="application/rsd+xml" title="RSD" href="https://wiert.wordpress.com/xmlrpc.php?rsd"> does exist.
Its’ href value can be obtained by querying document.querySelector('link[rel="EditURI"]').href and truncate it, so I made some conditional code that first tries the HighlanderComments and defers code obtaining it from the link element I mentioned above.
I also added proper Bookmarklet wrappers so the function results don’t leak to the console or Browser (Firefox really does not like Bookmarklets without this wrapper).
javascript:(function(){
//Statements returning a non-undefined type, e.g. assignments
})();
Firefox also dislikes pasting code into the development console.
Code:
Posted in Bookmarklet, Chrome, Development, Firefox, JavaScript/ECMAScript, Power User, Scripting, Software Development, Web Browsers | Leave a Comment »
Posted by jpluimers on 2024/07/17
The feature reminds me on how archive.today saves content.
Both the zhot and tweetzhot repositories are on my list of tools to try. They might make writing blog posts easier.
They are both based on [Wayback/Archive] puppeteer/puppeteer: Headless Chrome Node.js API
…
Puppeteer is a Node library which provides a high-level API to control Chrome or Chromium over the DevTools Protocol. Puppeteer runs headless by default, but can be configured to run full (non-headless) Chrome or Chromium.…
It demonstrates headless browser usage and can for instance:
- Generate screenshots and PDFs of pages.
- Crawl a SPA (Single-Page Application) and generate pre-rendered content (i.e. “SSR” (Server-Side Rendering)).
- Automate form submission, UI testing, keyboard input, etc.
- Create an up-to-date, automated testing environment. Run your tests directly in the latest version of Chrome using the latest JavaScript and browser features.
- Capture a timeline trace of your site to help diagnose performance issues.
- Test Chrome Extensions.
Note any headless browser will have some trouble rendering single-page applications.
Repositories:
Posted in Chrome, Chrome, Development, Google, JavaScript/ECMAScript, Power User, Puppeteer, Scripting, Software Development, Web Browsers | Leave a Comment »