I remember having to use Javascript to generate the image path (I cannot quite remember why absolute or root-relative URLs were not an option for us though...)
359 karma · joined March 21, 2013
I remember having to use Javascript to generate the image path (I cannot quite remember why absolute or root-relative URLs were not an option for us though...)
<font face="Wingdings">J</font>
Which renders as a smiley face.It helps with pasting special chars, newlines, and remote sessions without access to the local clipboard.
secret=$(vipe)
echo "$secret"
https://manpages.debian.org/jessie/moreutils/vipe.1It was a strange laptop. MXM socketed GPU, 120Hz screen that came with Nvidia 3DVision shutter glasses, and the worst battery life I've ever experienced.
> If an organiser turns on automated goal setting, GoFundMe adjusts their goal automatically based on the fundraiser’s characteristics and performance. You can see the goal history if GoFundMe has ever made automatic updates.
> To help the organiser reach their goal, we start them at a lower goal and adjust it as donations come in.
But on the other hand, since document.write (rightfully) gets such little usage - and has a multitude of footguns - I wouldn't be surprised if browsers used a different, slower code path when executing it; if only to prevent it from borking the parser.
function numbers() {
yield from [1,2,3];
yield from [4,5,6];
};
foreach (numbers() as $k => $v) { echo "$k => $v\n"; }
0 => 1
1 => 2
2 => 3
0 => 4
1 => 5
2 => 6The biggest missing scroll-snap feature I see is the ability to tell a scrolling container to "snap to the next position in this direction", and maybe by extension "which element(s) are currently snapped". In this article clicking an arrow moves the scroll position by a fixed 40px, but it would be very nice to have a proper API that accounts for element sizes, snap alignments, out-of-axis children, etc.
I ended up writing a package a few years ago that does this (scroll-snap-api). It feels so dirty to calculate the styles on every child in the tree just to find scroll snap positions.
https://github.com/tc39/proposal-pipeline-operator
I'm very excited for it.
I just tested it locally to check and it works fine.
And these overrides can be applied to local fonts as well (generally used to ensure the metrics of the local fallback font matches the yet-to-be-downloaded web font, preventing a layout shift when the web font is swapped in)
ascent-override - https://developer.mozilla.org/en-US/docs/Web/CSS/@font-face/...
descent-override - https://developer.mozilla.org/en-US/docs/Web/CSS/@font-face/...
line-gap-override - https://developer.mozilla.org/en-US/docs/Web/CSS/@font-face/...
size-adjust - https://developer.mozilla.org/en-US/docs/Web/CSS/@font-face/...
The image was essentially a simple checksum. Each user would eventually memorise which icon was "theirs".
test
example
invalid
localhost
local
localdomain
domain
lan
home
host
corp
0. https://www.ietf.org/archive/id/draft-chapin-rfc2606bis-00.h...If an attacker is capable of installing apps on your server... you've already lost.
0. https://devblogs.microsoft.com/oldnewthing/20060508-22/?p=31...
An example: I don't really want to add a click event listener to a link to make it display in a modal (or whatever). Because this event is too low-level and now my listener needs to check modifier keys. What I really want is to somehow tell the browser "if the current window URL is about to change via this anchor element, call this function instead". The user is still free to open their links in new windows or tabs and my code will not be triggered for those cases.
A CSS example: I don't really want to set cursor images for every element and pseudo-class. I'm forced to list every element that uses the cursor I'm overriding. What I really want is to tell the browser "use this custom cursor image wherever you were going to use the default (hand/wait/resize/etc) cursor". My code would then be future-proofed for new elements/UI.
Sometimes I feel that certain browser APIs suffer from the XY problem.
A 20 MPG car is not twice as efficient as a 10 MPG car.
http://www.mpgillusion.com/p/what-is-mpg-illusion.html
L/100km has the length and volume units reversed, which allows comparisons.
For example: prevent changing the top-level category of a product. E.g. Shoes should not be allowed to become camera gear.
If two packages I require depend on incompatible versions of some third package, there aren't any easy ways for me to resolve it.
This problem exists because of the global nature of PHP namespaces.
https://web.archive.org/web/20131201024352/http://www.sitepo...