solid

Describe the bug after the reproduction finishes the initial load. clicking the reload button triggers a signal update, that signal used in multiple places in the application to refresh its dependents. the signal is always read via a wrapper function that read it via so this signal should never get entangled. the assumption that any owner reading that refresh signal, can re execute(unless it is held by another entanglement) but that signal read itself should not cause entanglement. between its readers. and we can see that works for the 3 top panels, each reload will reset the tab and show its fallback until it is resolved the tabs independently resolve however the TabPanel values are only updated on the initial click, and if we click it again while the top panels are still resolving, we will only see them going back to fallback, but the values of the Tab do not get updated even though they have only 20ms resolve time. any effect on the refresh signal will not trigger until everything settles Your Example Website or App https://s.olid.uk/id/pEAxMQSvTAqDiwR6cEoeWw (2.0.0-rc.6) playground @ 2.0.0-beta.15 Steps to Reproduce the Bug or Issue 1. wait for initial load of all panels 2. click reload once , then again , then again, you will see top 3 panels reset to fallback but the TabPanel holding the values from the first reload click 3. once we stop clicking reload and we let all panels resolve the TabPanel will update its new values Expected behavior it is not clear why TabPanel will hold the render, we can also isolate TabPanel to only depend on the refresh signal without any other dependencies, and the render will still block. for example by generating random data without async in the code. this might be miss understanding, but it is hard to trace that easily. additionally tried the same reproduction with older version like 2.0.0-rc.15 and the Tab data updates with every reload click. Screenshots or Videos ##2.0.0-rc.6 2.0.0-beta.15 Platform OS: [e.g. macOS, Windows, Linux] Browser: [e.g. Chrome, Safari, Firefox] Version: [e.g. 91.1] Additional context playground source files (json)

Describe the bug Doesn't work at all, elementRef never becomes assigned. But this is fully allowed by the type system and compiles Works as intended So I'm guessing either this is a bug or it simply shouldn't compile if it's not meant to be supported. Your Example Website or App See description Steps to Reproduce the Bug or Issue Just put a ref variable inside the ref array like ref={[myRef]} and it will never be assigned. Expected behavior Either a compile error if this isn't intended or the ref element to be successfully assigned Screenshots or Videos _No response_ Platform OS: [Windows] Browser: Chrome Version: [152] Additional context _No response_

Closes #3285 What was broken `elref={el}elref={[el]}_$ref(() => [el], element)elf && f(element)undefinedundefinedletref={[el]}ref={[obj.el]}ref={[[el]]}ref={[...refs]}ref={[fn]}constundefinedundefinednullfalselet cb = someFn; someFncbpackages/web/test/ref-array.spec.tsxconstJSX_COMPILER=babelrefArraysclippy -D warnings@solidjs/babel-plugin@solidjs/compiler`.