25 Matching Annotations
  1. Jan 2024
  2. Sep 2023
  3. Sep 2022
    1. Thats because you have both width and padding set to one element. And by default padding is added on top of width. (Making it 100% + 2*30px of width). #header{ padding: 30px; width: 100%; } Either remove padding and add it to an inner element with no width set, or use: box-sizing: border-box; Which makes the width calculation include padding. :)
  4. Aug 2022
    1. then two different listeners/renderers switching magically between each other based on the header being present or not, without the end user being informed or clear about this
  5. Mar 2022
    1. The last note is that when binding commands to keyboard shortcuts it is often necessary to only have one command, not two commands connected with a pipe like we use above. You can accomplish this by invoking your piped command as a command string argumetn to a new shell like this:
    1. The reason for the new name is that the "dist-upgrade" name was itself extremely confusing for many users: while it was named that because it was something you needed when upgrading between distribution releases, it sounded too much as though it was only for use in that circumstance, whereas in fact it's much more broadly applicable.
  6. Sep 2021
  7. Oct 2020
    1. When using a method in a top-level object to modify its state, such object isn't updated either.
    2. There have been a number of issues opened about this, and a good deal of confusion. The docs indicate that if you mutate an object without there being a = involved, this doesn't trigger an update. But there's no mention that only assignments to certain variables trigger updates.
  8. Sep 2020
    1. This is likely not desired for ES module dependencies: Here require should usually return the namespace to be compatible with how bundled modules are handled. If you set esmExternals to true, this plugins assumes that all external dependencies are ES modules and will adhere to the requireReturnsDefault option. If that option is not set, they will be rendered as namespace imports.
  9. Jul 2020
  10. May 2020
    1. Many also question how the average user with little knowledge of the GDPR will react to being asked so many questions regarding consent. Will they be confused? Probably at first. It will be up to each business to create a consent form that is easy to understand, while being at the same time comprehensive and informative
    1. P ⇒ Q

      It may be confusing for a newcomer (or on first read-through) that the variable/predicate/condition that represents the "necessary condition" in this statement P ⇒ Q is the Q.

      One might be forgiven for incorrectly assuming that the P represents the necessary condition. That is because most of the time when one states a statement/relation/implication/etc. about a subject, the sentence/statement begins with the subject. For example, if we're explaining about a "less than" relationship, and we give x < y as an example, one would correctly assume that x is the subject here and x is the thing that is less than.

      So it may be a bit surprising to a newcomer (on first read-through) that the subject of this section — the necessary condition — is represented by the Q and not be the P.

      (Made even more confusing by the fact that the very same implication P ⇒ Q is also used to express the opposite sufficiency relationship in the very next section. I would argue that Q ⇒ P should have been used instead in exactly one of these sections to make it clearer that the subject is different and/or the relation is different, depending how you look at it.)

      Is there any reason we couldn't rewrite this to express the logical relation between P and Q with the subject first? If we let P be the subject (that is, "necessary condition" that we're illustrating/explaining), could we not rewrite this as P ⇐ Q?

      In fact, that is exactly how this relation was expressed below, in https://en.wikipedia.org/wiki/Necessity_and_sufficiency#Simultaneous_necessity_and_sufficiency !:

      that P is necessary for Q, P ⇐ Q, and that P is sufficient for Q, P ⇒ Q

    2. In algebra, for some set S together with an operation ⋆ {\displaystyle \star } to form a group, it is necessary that ⋆ {\displaystyle \star } be associative.

      Seems like a simpler example (of individually necessary and jointly sufficient) that is easier to follow could be found.

  11. Apr 2020
    1. it isn't actually -prune itself that causes this, by the way. The issue is that the or operator "short-circuits", and or has lower precedence than and. The end result is that if a file called .snapshot is encountered it will match the first -name, -prune will then do nothing (but return true), and then the or returns true since its left-argument was true. The action (eg: -print) is part of its second argument, so it never has a chance to execute.
  12. Mar 2020
    1. Are cookies governed by the GDPR? Cookie usage and it’s related consent acquisition are not governed by the GDPR, they are instead governed by the ePrivacy Directive (Cookie Law) which in future will be repealed by the up-coming ePrivacy Regulation.
  13. Feb 2020
  14. Nov 2019
    1. I'm considering this, although I'm still leaning towards not including it and I'd love to just get rid of first if it wouldn't break so many peoples tests. Newcomers to Capybara don't understand (or aren't willing to learn) the issues that all/first (and last if added) have and massively overuse them. Yes the fact that all and first now wait by default will prevent some of the new user issues/confusion, but it won't fix the non-reloadability issue.