Creează un cont pentru a te abona la acest blog și a-i urmări articolele pe pagina Lectură.
-
The Chrome DevTools MCP is very useful!
-
The following are my notes on investigating a bug that a customer ran into back when I was on the WebView2 team.
-
Before working in Chromium I had been using our internal project's Azure DevOps (ADO) code search feature, and occassionally using Chromium Code Search or GitHub's code search.
-
I've made WatchBuildLog, a VS Code extension that watches a build log file and parses out build errors for the VS Code Problems tab.
-
I've had trouble getting Time Travel Debugging (TTD) working with debugging WPT from my chromium repo on Windows.
-
I've been writing (and using) a browser extension called OpenSourceIn that allows you to open the source code you're viewing in the browser into VS Code.
-
I'm happy to have finished my first Chromium bug that adds a WPT.
-
Previously, I made an Eleventy based GitHub project with GitHub automation to run Eleventy when checking in changes and hooked up a custom subdomain to the GitHub pages thinking I would start a new domain for the new blog.
-
I've made a sticky header that scroll animates all using CSS.
-
Previously, I made an Eleventy based GitHub project with GitHub automation to run Eleventy when checking in changes.
-
I wanted to replace my existing blog solution with a simple markdown setup.
-
SysInternals is in the Windows Store?
-
So much has to go right to get a 404.
-
JavaScript has a type Proxy that lets you intercept all interactions with an object - all property reads, writes, method calls, and so on.
-
JavaScript arrays are unbelievable.
-
Its rare to find devs anticipating Unicode control characters showing up in user input.
-
The scrollbars in UWP WebView and in Edge have different default behavior leading to many emails to my team.
-
There are two main differences in terms of security between a JavaScript UWP app and the Edge browser: Process Model A JavaScript UWP app has one process (technically not true with background tasks and other edge cases but ignoring that for the moment) th…
-
There's no perfect way to change the user agent string for the UWP WebView (x-ms-webview in HTML, Windows.UI.Xaml.Controls.WebView in XAML, and Windows.Web.UI.Interop.WebViewControl in Win32) but there are two imperfect methods folks end up using.
-
The GoBack and GoForward methods on the UWP WebView (x-ms-webview in HTML, Windows.UI.Xaml.Controls.WebView in XAML, and Windows.Web.UI.Interop.WebViewControl in Win32) act the same as the Back and Forward buttons in the Edge browser.
-
If you're developing with the new Windows.Web.UI.Interop.WebViewControl you may have noticed you cannot navigate to localhost HTTP servers.
-
Folks familiar with JavaScript UWP apps in Win10 have often been confused by what PWAs in Win10 actually are.
-
JSBrowser is a basic browser built as a Win10 JavaScript UWP app around the WebView HTML element.
-
JSBrowser is a basic browser built as a Win10 JavaScript UWP app around the WebView HTML element.
-
Win10 Changes In Win8.1 JavaScript UWP apps we supported multiple windows using MSApp DOM APIs.
-
The documentation for printing in JavaScript UWP apps is out of date as it all references MSApp.getHtmlPrintDocumentSource but that method has been replaced by MSApp.getHtmlPrintDocumentSourceAsync since WinPhone 8.1.
-
The x-ms-webview HTML element has the void addWebAllowedObject(string name, any value) method and the webview XAML element has the void AddWebAllowedObject(String name, Object value) method.
-
Previously I described Application Content URI Rules (ACUR) parsing and ACUR ordering.
-
JavaScript Microsoft Store apps have some details related to activation that are specific to JavaScript Store apps and that are poorly documented which I’ll describe here.
-
Application Content URI Rules (ACUR from now on) defines the bounds on the web that make up a Microsoft Store application.
-
Application Content URI Rules (ACUR from now on) defines the bounds of the web that make up the Microsoft Store application.
-
Since I had last posted about using Let's Encrypt with NearlyFreeSpeech, NFS has changed their process for setting TLS info.
-
Parsing WinMD files, the containers of WinRT API metadata, is relatively simple using the appropriate .NET reflection APIs.
-
I've put my WPAD Fiddler extension source and the installer on GitHub.
-
The other day I had to debug a JavaScript UWA that was failing when trying to use an undefined property.
-
I've made a PowerShell script to show system toast notifications with WinRT and PowerShell.
-
TL;DR: Web content in a JavaScript Windows Store app or WebView in a Windows Store app that has full access to WinRT also gets to use XHR unrestricted by cross origin checks.
-
You can call WinRT APIs from PowerShell.
-
You can use conditional breakpoints and debugging commands in windbg and cdb that together can amount to effectively patching a binary at runtime.
-
2016-Nov-5: Updated post on using Let's Encrypt with NearlyFreeSpeech.net I use NearlyFreeSpeech.net for my webhosting for my personal website and I've just finished setting up TLS via Let's Encrypt.
-
I've made a Unicode Clock in JavaScript.
-
I've put a new app on the Windows Store: Cloud Share.
-
Some time back while I was working on getting the Javascript Windows Store app platform running on Windows Phone (now available on the last Windows Phone release!)
-
The DOM location interface exposes the HTML document's URI parsed into its properties.
-
I just got a FitBit One from my wife.
-
PowerShell nicely includes ConvertTo-CSV and ConvertFrom-CSV which allow you to serialize and deserialize your PowerShell objects to and from CSV.
-
Occasionally I have need to run a set of unrelated promises in series, for instance an object dealing with a WinRT camera API that can only execute one async operation at a time, or an object handling postMessage message events and must resolve associated…
-
When writing a JavaScript library that uses postMessage and the message event, I must be considerate of other JS code that will be running along side my library.