itaibn
Solution: Using a sha256="..." attribute should only allow you to access files that were initially loaded with a tag that has a sha256 attribute, and this attribute is only used for resources the developer considers public.
No they don't. There is a law known as [Huygens' principle](https://en.wikipedia.org/wiki/Huygens%E2%80%93Fresnel_princi...) which says that when a disturbance at a particular point creates a wave, that wave only propagates on an outwards-expanding sphere that is centered at that point of disturbance, and does not produce any effect on the interior of that sphere. This was originally formulated for light waves, but it also holds for other kinds of waves, such as sound waves or, in this case, gravitational waves. What this means is that when you look at something that's far away you see a sharp image of exactly what happened there a short time ago (the time it had taken the light to reach you), whereas if the principle did not hold, each light source would have a small "echo" after it which would blur the image.
However, one of the reasons Huygens' principle holds is that the waves are propagating over three dimensions. In contrast, water waves only propagate over two dimensions, so Huygens' principle fails. That is why ripples continue to emanate from a spot even long after the disturbance there is over. More generally, Huygens' principle holds whenever the number of dimensions is odd and fails whenever the number of dimensions is even.
[Note: I may be wrong on why Huygens' principle fails for water waves. Water waves are actually pretty complicated compared to other kinds of waves and I am not knowledgeable in all the subtleties.]
(Well, the text file has empty lines separating the comments and example strings so it technically includes the empty string, but it's not in the JSON file.)
* The number may have optional sign and digits after a decimal point, and may use exponential notation. Example: (-1.2e1, .0E+0, 1.e-3) => "Yes". As seen in the second and third number here, there may be no digits before or after the decimal point, but both at the same time (i.e., ".0" and "0." parse but not ".").
* If the number begins with "0x" or "0X" it is read in hexadecimal, where the digits a-f may be in either case. Hexadecimal notation must not be accompanied by decimal point, sign, or exponential notation.
* No whitespace is permitted within the numeral, even between the sign and the digits as in "+ 11", but both tabs and spaces may be used before and after the numeral without changing its value. In particular, by using a input of the form "1 " it is possible to make rectangular display empty while still parsing it as number. Note that pressing "Check" leads to the numbers being displayed in the rectangle in exactly the same way as they were displayed in the text box, which may depend on the position of the cursor in the text box.
ETA: Also, you mentioned rounding, but there is also exponent overflow and underflow. The application refuses to parse numbers greater or equal to 1.7976932e308. It parses arbitrary negative exponents fine, but it does not recognize that 1e-324 is greater than 0.