9 Matching Annotations
  1. Nov 2023
    1. Google Chrome for Android no longer has an option to disable “Pull to Refresh”. For people who don’t really like using this feature, this is pretty annoying. There was a way to disable this using a flag, but version 75 removed this flag too.
    2. I was filling and completing a report on a website, uploaded an attachment just wanted to fill up some remaining inputs on final step, while scrolling down the whole page refreshed!.. hours of work and composition was gone instantly, extremely frustrating!
    3. I stoped using chrome android for purchases, due to the refresh occuring while scrolling up. Poor design choice
  2. Jan 2023
    1. There is no predetermined correlation between this import path and the file system, and the imported module doesn’t have to know anything about the import path used in an importing module.

      This is not a good approach. It's the opposite of what you want. Module resolution remains easy for computers (because of their speed), but tedious for humans.

      As a writer, maybe there's some benefit for no correlation. As a reader trying to understand a foreign codebase, esp. one who is in the moment trying to figure out, "Where is this thing defined? Where can I read the source code?" when jumping through procedure definitions, not being able to trivially ascertain which file a given thing is in is unnecessary friction. Better to offload a tiny bit of work onto the author who knows the codebase (or at least their own immediate intention) well rather than to stymie the progress of dozens/hundreds of readers trying to work things out.

  3. Feb 2022
  4. Oct 2021
    1. So if I just forward the cookie header (which contains the access-token), wouldn't that be just what I am not supposed to do. I mean what's the point of using 'HttpOnly' flag if I return the token to the client-side js on every request.