25 Matching Annotations
  1. Jun 2021
  2. May 2021
    1. The simple problem that I see with fragment identifiers is that their existence and functionality relies completely on the developer rather than the browser. Yes, the browser needs to read and interpret the identifier and identify the matching fragment. But if the developer doesn’t include any id attributes in the HTML of the page, then there will be no identifiable fragments. Do you see why this is a problem? Whether the developer has coded identifiers into the HTML has nothing to do with whether or not the page actually has fragments. Virtually every web page has fragments. In fact, sectioning content as defined in the HTML5 spec implies as much. Every element on the page that can contain content can theoretically be categorized as a “fragment”.

      at the mercy of author

  3. Feb 2021
  4. Dec 2020
  5. Nov 2020
    1. Another possible syntax is {#slot bar}<Foo/>{/slot}, which would also allow a bunch of DOM nodes and components inside the slot, without them needing to be from a single component

      I like it

  6. Oct 2020
  7. Sep 2020
    1. Syntax-wise, I would like to be able to pass id, style and class DOM attributes as well as (ideally) svelte props to whatever the slot was replaced with, so prefixing everything with attr in the slot that should be passed sounds like a good idea. Examples: <slot attr:class=“test” attr:class:active={true} /> or <slot attr:style=“color: red” attr:id=“henlo” />
  8. Jul 2020
  9. Jun 2020
    1. Sometimes, the line between 'bug' and 'feature' is a hard one to draw. Generally, a feature is anything that adds new behavior, while a bug is anything that causes incorrect behavior. Sometimes, the core team will have to make a judgment call.
  10. Nov 2019
    1. I often wish for this. I don't understand why this hasn't been added.

      Ugly workaround for now:

      # Note, even though we don't need or use arguments passed to this selector, you *must* pass in an
      # argument to prevent it from matching the :id selector and giving a "Unable to find id :parent (Capybara::ElementNotFound)" error.
      # Example: el.first(:parent, 1)
      # You may also need match: first if el matches multiple elements to avoid Capybara::Ambiguous
      Capybara.add_selector(:parent) do
        xpath { ".//.." }
      end
      
  11. Oct 2019