18 Matching Annotations
  1. Oct 2020
  2. 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” />
  3. Jul 2020
  4. 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.
  5. 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
      
  6. Oct 2019