finding(plugin-gantt/plugin-list): one authored view filter reaches the wire in two dialects — ListView forwards it, the gantt path recompiles it through mergeFilterNodes #7221

Closed
Closed
finding(plugin-gantt/plugin-list): one authored view filter reaches the wire in two dialects — ListView forwards it, the gantt path recompiles it through mergeFilterNodes#7221
Labels
domain:uiobjectui ui stream: fix lands on the published library or apps — objectui execution seatpriority:p2

Description

@os-warren
os-warren
opened on Sep 1, 2026

Blocked-by: #7349

Recorded while implementing half 1 of objectui#7210. Filed separately because objectui#7210's ruling scoped the dialect disagreement OUT of that card: "if half 3's condition fails and both requests survive, the dialect mismatch is a finding to report, not to repair here." Half 3's condition did fail (the paged request has consumers other than the footer), so both requests survive and this needs its own home. Not a duplicate of objectui#7210 — that card is about the footer and the ceiling; this one is about the two shapes.

Filed unassigned, as an observation. I have not established that the two dialects ever select different rows; that is the first thing to measure and it is why this is worth a card rather than a note.

Measured 2026-09-02 (PR #7348, test-only pins): DIVERGENT. On the wire the two dialects are equivalent (the server lowers both to the same $and); through ValueDataSource they are not, because the in-memory matcher reads neither the flat implicit-AND array nor the null-ness operators. The correctness half is #7349; this card closes when the two it.fails cases named "diverges — objectui#7221" in packages/core/src/utils/__tests__/filter-dialect-equivalence-7221.test.ts flip to plain it there.

What the reporter saw

objectui#7210 measured one page load of a type: 'gantt' list view against published @objectstack/* 17.2.0 and got two requests whose filters do not agree:

paged filter=[["visible_from","is_not_null"],["due_date","is_not_null"]]
unbounded filter=["and",["visible_from","isnotnull",null],["due_date","isnotnull",null]]

Same authored view, same load, two wire shapes.

The two paths, read rather than assumed

  • ListView's own query forwards the authored value.buildEffectiveFilter(schema.filter, currentFilters, userFilterConditions) returns the authored array unchanged when it is the only surviving source. Measured in a harness (18 rows, pagination.pageSize: 6, authored filter [["visible_from","is_not_null"],["due_date","is_not_null"]]): the paged request went out carrying that array verbatim.

  • The gantt's own query goes through a compiler that ListView's does not.plugin-gantt/src/index.tsx declares OBJECT_GANTT_DATA_SOURCE = { filter: true, sort: true }, so ElementDataSourceGate (packages/react/src/element-data-source/ElementDataSourceGate.tsx) runs mergeFilterNodes(base.filter, composed.filter) before ObjectGantt ever reads schema.filter. mergeFilterNodes (packages/core/src/utils/filter-converter.ts) returns a lone surviving source as-is and wraps two or more as ["and", ...nodes] — with toFilterNode lowering any ViewFilterRule element to an AST node on the way through.

So the divergence is not random: it is one path composing and lowering where the other forwards. With a single filter source the two agree (my harness reproduced exactly that — both requests carried the flat authored array); with two or more surviving sources on the gantt side only, they part.

Why it is worth a card

  1. The compilation is where a wrong answer could hide. Wrapping and operator lowering both change what the server matches if either side is imperfect. Nobody has checked that ["and", A, B] and [A, B] select the same rows through every adapter — @object-ui/data-objectstack maps is_not_null to isnotnull on the way out, and the two shapes reach that mapping through different amounts of normalization.
  2. It makes the two requests hard to reason about as "the same rows twice." objectui#7210's half 3 is explicitly NOT "dedupe the requests", precisely because deduping means picking one of these dialects and picking wrong changes the result set silently. That decision cannot be taken until somebody has established the two are equivalent.
  3. It is a divergence between siblings, not a property of one. Whatever the answer is, one authored filter should have one lowered form.

Suggested first step

Not a fix, a measurement: take an authored two-rule filter with two surviving sources, run both lowered shapes through ValueDataSource and through ObjectStackAdapter's serializer, and compare the row sets and the wire strings. If they agree, this is a tidiness card; if they do not, it is a correctness one and the severity moves.

Refs: objectui#7210 (parent observation, halves 2 and 3 still open there) · PR #7348 (the measurement pins) · #7349 (the correctness fix this card is blocked on).

Metadata

Metadata

Assignees

No one assigned

    Labels

    domain:uiobjectui ui stream: fix lands on the published library or apps — objectui execution seatpriority:p2

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      , 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Add copy buttons to all 
       blocks\n(function() {\n function addCopyButtons() {\n document.querySelectorAll('pre code').forEach(function(codeBlock) {\n if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;\n codeBlock.parentElement.setAttribute('data-copy-added', 'true');\n \n var btn = document.createElement('button');\n btn.textContent = 'Copy';\n btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';\n btn.onmouseover = function() { this.style.opacity = '1'; };\n btn.onmouseout = function() { this.style.opacity = '0.7'; };\n btn.onclick = function() {\n navigator.clipboard.writeText(codeBlock.textContent).then(function() {\n btn.textContent = 'Copied!';\n setTimeout(function() { btn.textContent = 'Copy'; }, 1500);\n });\n };\n codeBlock.parentElement.style.position = 'relative';\n codeBlock.parentElement.appendChild(btn);\n });\n }\n \n addCopyButtons();\n \n // Re-run on dynamic content\n var observer = new MutationObserver(addCopyButtons);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Add Copy Buttons to Code Blocks");
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '

      Skip to content
      finding(plugin-gantt/plugin-list): one authored view filter reaches the wire in two dialects — ListView forwards it, the gantt path recompiles it through mergeFilterNodes #7221
      Closed
      Closed
      finding(plugin-gantt/plugin-list): one authored view filter reaches the wire in two dialects — ListView forwards it, the gantt path recompiles it through mergeFilterNodes#7221
      Labels
      domain:uiobjectui ui stream: fix lands on the published library or apps — objectui execution seatpriority:p2
      Description
      @os-warren
      os-warren
      opened on Sep 1, 2026
      Blocked-by: #7349
      Recorded while implementing half 1 of objectui#7210. Filed separately because objectui#7210's ruling scoped the dialect disagreement OUT of that card: "if half 3's condition fails and both requests survive, the dialect mismatch is a finding to report, not to repair here." Half 3's condition did fail (the paged request has consumers other than the footer), so both requests survive and this needs its own home. Not a duplicate of objectui#7210 — that card is about the footer and the ceiling; this one is about the two shapes.
      Filed unassigned, as an observation. I have not established that the two dialects ever select different rows; that is the first thing to measure and it is why this is worth a card rather than a note.
      Measured 2026-09-02 (PR #7348, test-only pins): DIVERGENT. On the wire the two dialects are equivalent (the server lowers both to the same $and); through ValueDataSource they are not, because the in-memory matcher reads neither the flat implicit-AND array nor the null-ness operators. The correctness half is #7349; this card closes when the two it.fails cases named "diverges — objectui#7221" in packages/core/src/utils/__tests__/filter-dialect-equivalence-7221.test.ts flip to plain it there.
      What the reporter saw
      objectui#7210 measured one page load of a type: 'gantt' list view against published @objectstack/* 17.2.0 and got two requests whose filters do not agree:
      paged filter=[["visible_from","is_not_null"],["due_date","is_not_null"]]
unbounded filter=["and",["visible_from","isnotnull",null],["due_date","isnotnull",null]]

      Same authored view, same load, two wire shapes.
      The two paths, read rather than assumed
      • ListView's own query forwards the authored value.buildEffectiveFilter(schema.filter, currentFilters, userFilterConditions) returns the authored array unchanged when it is the only surviving source. Measured in a harness (18 rows, pagination.pageSize: 6, authored filter [["visible_from","is_not_null"],["due_date","is_not_null"]]): the paged request went out carrying that array verbatim.
      • The gantt's own query goes through a compiler that ListView's does not.plugin-gantt/src/index.tsx declares OBJECT_GANTT_DATA_SOURCE = { filter: true, sort: true }, so ElementDataSourceGate (packages/react/src/element-data-source/ElementDataSourceGate.tsx) runs mergeFilterNodes(base.filter, composed.filter) before ObjectGantt ever reads schema.filter. mergeFilterNodes (packages/core/src/utils/filter-converter.ts) returns a lone surviving source as-is and wraps two or more as ["and", ...nodes] — with toFilterNode lowering any ViewFilterRule element to an AST node on the way through.
      So the divergence is not random: it is one path composing and lowering where the other forwards. With a single filter source the two agree (my harness reproduced exactly that — both requests carried the flat authored array); with two or more surviving sources on the gantt side only, they part.
      Why it is worth a card
      1. The compilation is where a wrong answer could hide. Wrapping and operator lowering both change what the server matches if either side is imperfect. Nobody has checked that ["and", A, B] and [A, B] select the same rows through every adapter — @object-ui/data-objectstack maps is_not_null to isnotnull on the way out, and the two shapes reach that mapping through different amounts of normalization.
      2. It makes the two requests hard to reason about as "the same rows twice." objectui#7210's half 3 is explicitly NOT "dedupe the requests", precisely because deduping means picking one of these dialects and picking wrong changes the result set silently. That decision cannot be taken until somebody has established the two are equivalent.
      3. It is a divergence between siblings, not a property of one. Whatever the answer is, one authored filter should have one lowered form.
      Suggested first step
      Not a fix, a measurement: take an authored two-rule filter with two surviving sources, run both lowered shapes through ValueDataSource and through ObjectStackAdapter's serializer, and compare the row sets and the wire strings. If they agree, this is a tidiness card; if they do not, it is a correctness one and the severity moves.
      Refs: objectui#7210 (parent observation, halves 2 and 3 still open there) · PR #7348 (the measurement pins) · #7349 (the correctness fix this card is blocked on).
      Metadata
      Metadata
      Assignees
      No one assigned
        Labels
        domain:uiobjectui ui stream: fix lands on the published library or apps — objectui execution seatpriority:p2
        Type
        No type
        Projects
        No projects
          Milestone
          No milestone
          Relationships
          None yet
          Development
          No branches or pull requests
          Issue actions
          
, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Force GitHub README to respect dark mode\n(function() {\n var style = document.createElement('style');\n style.textContent = '\n .markdown-body {\n color-scheme: dark light;\n }\n .markdown-body pre { background: #161b22 !important; }\n .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }\n .markdown-body table th, .markdown-body table td { border-color: #30363d !important; }\n .markdown-body img { background: #0d1117; }\n .markdown-body blockquote { border-left-color: #8b949e; }\n .markdown-body hr { border-color: #30363d; }\n ';\n document.head.appendChild(style);\n})();", "GitHub Dark Mode README Fix");
}
} catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

          Skip to content
          finding(plugin-gantt/plugin-list): one authored view filter reaches the wire in two dialects — ListView forwards it, the gantt path recompiles it through mergeFilterNodes #7221
          Closed
          Closed
          finding(plugin-gantt/plugin-list): one authored view filter reaches the wire in two dialects — ListView forwards it, the gantt path recompiles it through mergeFilterNodes#7221
          Labels
          domain:uiobjectui ui stream: fix lands on the published library or apps — objectui execution seatpriority:p2
          Description
          @os-warren
          os-warren
          opened on Sep 1, 2026
          Blocked-by: #7349
          Recorded while implementing half 1 of objectui#7210. Filed separately because objectui#7210's ruling scoped the dialect disagreement OUT of that card: "if half 3's condition fails and both requests survive, the dialect mismatch is a finding to report, not to repair here." Half 3's condition did fail (the paged request has consumers other than the footer), so both requests survive and this needs its own home. Not a duplicate of objectui#7210 — that card is about the footer and the ceiling; this one is about the two shapes.
          Filed unassigned, as an observation. I have not established that the two dialects ever select different rows; that is the first thing to measure and it is why this is worth a card rather than a note.
          Measured 2026-09-02 (PR #7348, test-only pins): DIVERGENT. On the wire the two dialects are equivalent (the server lowers both to the same $and); through ValueDataSource they are not, because the in-memory matcher reads neither the flat implicit-AND array nor the null-ness operators. The correctness half is #7349; this card closes when the two it.fails cases named "diverges — objectui#7221" in packages/core/src/utils/__tests__/filter-dialect-equivalence-7221.test.ts flip to plain it there.
          What the reporter saw
          objectui#7210 measured one page load of a type: 'gantt' list view against published @objectstack/* 17.2.0 and got two requests whose filters do not agree:
          paged filter=[["visible_from","is_not_null"],["due_date","is_not_null"]]
unbounded filter=["and",["visible_from","isnotnull",null],["due_date","isnotnull",null]]

          Same authored view, same load, two wire shapes.
          The two paths, read rather than assumed
          • ListView's own query forwards the authored value.buildEffectiveFilter(schema.filter, currentFilters, userFilterConditions) returns the authored array unchanged when it is the only surviving source. Measured in a harness (18 rows, pagination.pageSize: 6, authored filter [["visible_from","is_not_null"],["due_date","is_not_null"]]): the paged request went out carrying that array verbatim.
          • The gantt's own query goes through a compiler that ListView's does not.plugin-gantt/src/index.tsx declares OBJECT_GANTT_DATA_SOURCE = { filter: true, sort: true }, so ElementDataSourceGate (packages/react/src/element-data-source/ElementDataSourceGate.tsx) runs mergeFilterNodes(base.filter, composed.filter) before ObjectGantt ever reads schema.filter. mergeFilterNodes (packages/core/src/utils/filter-converter.ts) returns a lone surviving source as-is and wraps two or more as ["and", ...nodes] — with toFilterNode lowering any ViewFilterRule element to an AST node on the way through.
          So the divergence is not random: it is one path composing and lowering where the other forwards. With a single filter source the two agree (my harness reproduced exactly that — both requests carried the flat authored array); with two or more surviving sources on the gantt side only, they part.
          Why it is worth a card
          1. The compilation is where a wrong answer could hide. Wrapping and operator lowering both change what the server matches if either side is imperfect. Nobody has checked that ["and", A, B] and [A, B] select the same rows through every adapter — @object-ui/data-objectstack maps is_not_null to isnotnull on the way out, and the two shapes reach that mapping through different amounts of normalization.
          2. It makes the two requests hard to reason about as "the same rows twice." objectui#7210's half 3 is explicitly NOT "dedupe the requests", precisely because deduping means picking one of these dialects and picking wrong changes the result set silently. That decision cannot be taken until somebody has established the two are equivalent.
          3. It is a divergence between siblings, not a property of one. Whatever the answer is, one authored filter should have one lowered form.
          Suggested first step
          Not a fix, a measurement: take an authored two-rule filter with two surviving sources, run both lowered shapes through ValueDataSource and through ObjectStackAdapter's serializer, and compare the row sets and the wire strings. If they agree, this is a tidiness card; if they do not, it is a correctness one and the severity moves.
          Refs: objectui#7210 (parent observation, halves 2 and 3 still open there) · PR #7348 (the measurement pins) · #7349 (the correctness fix this card is blocked on).
          Metadata
          Metadata
          Assignees
          No one assigned
            Labels
            domain:uiobjectui ui stream: fix lands on the published library or apps — objectui execution seatpriority:p2
            Type
            No type
            Projects
            No projects
              Milestone
              No milestone
              Relationships
              None yet
              Development
              No branches or pull requests
              Issue actions
              
, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Highlight search terms from Google/DuckDuckGo/Bing referrer\n(function() {\n var ref = document.referrer;\n var terms = [];\n \n if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {\n var url = new URL(ref);\n var q = url.searchParams.get('q') || url.searchParams.get('p');\n if (q) {\n terms = q.split(/\\s+/).filter(function(t) { return t.length > 2; });\n }\n }\n \n if (terms.length === 0) return;\n \n var style = document.createElement('style');\n style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';\n document.head.appendChild(style);\n \n function highlight(node) {\n if (node.nodeType === 3) { // text node\n var text = node.textContent;\n var found = false;\n terms.forEach(function(term) {\n var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\\]\\\\]/g, '\\\\') + ')', 'gi');\n if (regex.test(text)) {\n found = true;\n var frag = document.createDocumentFragment();\n var parts = text.split(regex);\n parts.forEach(function(part, i) {\n if (i % 2 === 0) {\n frag.appendChild(document.createTextNode(part));\n } else {\n var span = document.createElement('span');\n span.className = 'userscript-highlight';\n span.textContent = part;\n frag.appendChild(span);\n }\n });\n node.parentNode.replaceChild(frag, node);\n }\n });\n } else if (node.nodeType === 1 && node.childNodes) { // element\n var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];\n if (!skipTags.includes(node.tagName)) {\n Array.from(node.childNodes).forEach(highlight);\n }\n }\n }\n \n highlight(document.body);\n \n // Re-highlight on dynamic content\n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1 || node.nodeType === 3) highlight(node);\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Highlight Search Terms");
}
} catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

              Skip to content
              finding(plugin-gantt/plugin-list): one authored view filter reaches the wire in two dialects — ListView forwards it, the gantt path recompiles it through mergeFilterNodes #7221
              Closed
              Closed
              finding(plugin-gantt/plugin-list): one authored view filter reaches the wire in two dialects — ListView forwards it, the gantt path recompiles it through mergeFilterNodes#7221
              Labels
              domain:uiobjectui ui stream: fix lands on the published library or apps — objectui execution seatpriority:p2
              Description
              @os-warren
              os-warren
              opened on Sep 1, 2026
              Blocked-by: #7349
              Recorded while implementing half 1 of objectui#7210. Filed separately because objectui#7210's ruling scoped the dialect disagreement OUT of that card: "if half 3's condition fails and both requests survive, the dialect mismatch is a finding to report, not to repair here." Half 3's condition did fail (the paged request has consumers other than the footer), so both requests survive and this needs its own home. Not a duplicate of objectui#7210 — that card is about the footer and the ceiling; this one is about the two shapes.
              Filed unassigned, as an observation. I have not established that the two dialects ever select different rows; that is the first thing to measure and it is why this is worth a card rather than a note.
              Measured 2026-09-02 (PR #7348, test-only pins): DIVERGENT. On the wire the two dialects are equivalent (the server lowers both to the same $and); through ValueDataSource they are not, because the in-memory matcher reads neither the flat implicit-AND array nor the null-ness operators. The correctness half is #7349; this card closes when the two it.fails cases named "diverges — objectui#7221" in packages/core/src/utils/__tests__/filter-dialect-equivalence-7221.test.ts flip to plain it there.
              What the reporter saw
              objectui#7210 measured one page load of a type: 'gantt' list view against published @objectstack/* 17.2.0 and got two requests whose filters do not agree:
              paged filter=[["visible_from","is_not_null"],["due_date","is_not_null"]]
unbounded filter=["and",["visible_from","isnotnull",null],["due_date","isnotnull",null]]

              Same authored view, same load, two wire shapes.
              The two paths, read rather than assumed
              • ListView's own query forwards the authored value.buildEffectiveFilter(schema.filter, currentFilters, userFilterConditions) returns the authored array unchanged when it is the only surviving source. Measured in a harness (18 rows, pagination.pageSize: 6, authored filter [["visible_from","is_not_null"],["due_date","is_not_null"]]): the paged request went out carrying that array verbatim.
              • The gantt's own query goes through a compiler that ListView's does not.plugin-gantt/src/index.tsx declares OBJECT_GANTT_DATA_SOURCE = { filter: true, sort: true }, so ElementDataSourceGate (packages/react/src/element-data-source/ElementDataSourceGate.tsx) runs mergeFilterNodes(base.filter, composed.filter) before ObjectGantt ever reads schema.filter. mergeFilterNodes (packages/core/src/utils/filter-converter.ts) returns a lone surviving source as-is and wraps two or more as ["and", ...nodes] — with toFilterNode lowering any ViewFilterRule element to an AST node on the way through.
              So the divergence is not random: it is one path composing and lowering where the other forwards. With a single filter source the two agree (my harness reproduced exactly that — both requests carried the flat authored array); with two or more surviving sources on the gantt side only, they part.
              Why it is worth a card
              1. The compilation is where a wrong answer could hide. Wrapping and operator lowering both change what the server matches if either side is imperfect. Nobody has checked that ["and", A, B] and [A, B] select the same rows through every adapter — @object-ui/data-objectstack maps is_not_null to isnotnull on the way out, and the two shapes reach that mapping through different amounts of normalization.
              2. It makes the two requests hard to reason about as "the same rows twice." objectui#7210's half 3 is explicitly NOT "dedupe the requests", precisely because deduping means picking one of these dialects and picking wrong changes the result set silently. That decision cannot be taken until somebody has established the two are equivalent.
              3. It is a divergence between siblings, not a property of one. Whatever the answer is, one authored filter should have one lowered form.
              Suggested first step
              Not a fix, a measurement: take an authored two-rule filter with two surviving sources, run both lowered shapes through ValueDataSource and through ObjectStackAdapter's serializer, and compare the row sets and the wire strings. If they agree, this is a tidiness card; if they do not, it is a correctness one and the severity moves.
              Refs: objectui#7210 (parent observation, halves 2 and 3 still open there) · PR #7348 (the measurement pins) · #7349 (the correctness fix this card is blocked on).
              Metadata
              Metadata
              Assignees
              No one assigned
                Labels
                domain:uiobjectui ui stream: fix lands on the published library or apps — objectui execution seatpriority:p2
                Type
                No type
                Projects
                No projects
                  Milestone
                  No milestone
                  Relationships
                  None yet
                  Development
                  No branches or pull requests
                  Issue actions
                  
, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Strip utm_, fbclid, gclid, etc. from all links on page\n(function() {\n var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',\n 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',\n 'ref', 'ref_src', 'source', 'medium', 'campaign'];\n \n function cleanUrl(url) {\n try {\n var u = new URL(url, window.location.origin);\n var changed = false;\n trackingParams.forEach(function(p) {\n if (u.searchParams.has(p)) {\n u.searchParams.delete(p);\n changed = true;\n }\n });\n return changed ? u.toString() : url;\n } catch (e) {\n return url;\n }\n }\n \n function cleanLinks() {\n document.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n \n cleanLinks();\n \n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1) {\n if (node.tagName === 'A') cleanLinks();\n node.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Remove Tracking Parameters from Links");
}
} catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); }
})();
(function(){
try {
var __m = "youtube.com";
var __re = new RegExp('^' + "youtube\\.com" + '

                  Skip to content
                  finding(plugin-gantt/plugin-list): one authored view filter reaches the wire in two dialects — ListView forwards it, the gantt path recompiles it through mergeFilterNodes #7221
                  Closed
                  Closed
                  finding(plugin-gantt/plugin-list): one authored view filter reaches the wire in two dialects — ListView forwards it, the gantt path recompiles it through mergeFilterNodes#7221
                  Labels
                  domain:uiobjectui ui stream: fix lands on the published library or apps — objectui execution seatpriority:p2
                  Description
                  @os-warren
                  os-warren
                  opened on Sep 1, 2026
                  Blocked-by: #7349
                  Recorded while implementing half 1 of objectui#7210. Filed separately because objectui#7210's ruling scoped the dialect disagreement OUT of that card: "if half 3's condition fails and both requests survive, the dialect mismatch is a finding to report, not to repair here." Half 3's condition did fail (the paged request has consumers other than the footer), so both requests survive and this needs its own home. Not a duplicate of objectui#7210 — that card is about the footer and the ceiling; this one is about the two shapes.
                  Filed unassigned, as an observation. I have not established that the two dialects ever select different rows; that is the first thing to measure and it is why this is worth a card rather than a note.
                  Measured 2026-09-02 (PR #7348, test-only pins): DIVERGENT. On the wire the two dialects are equivalent (the server lowers both to the same $and); through ValueDataSource they are not, because the in-memory matcher reads neither the flat implicit-AND array nor the null-ness operators. The correctness half is #7349; this card closes when the two it.fails cases named "diverges — objectui#7221" in packages/core/src/utils/__tests__/filter-dialect-equivalence-7221.test.ts flip to plain it there.
                  What the reporter saw
                  objectui#7210 measured one page load of a type: 'gantt' list view against published @objectstack/* 17.2.0 and got two requests whose filters do not agree:
                  paged filter=[["visible_from","is_not_null"],["due_date","is_not_null"]]
unbounded filter=["and",["visible_from","isnotnull",null],["due_date","isnotnull",null]]

                  Same authored view, same load, two wire shapes.
                  The two paths, read rather than assumed
                  • ListView's own query forwards the authored value.buildEffectiveFilter(schema.filter, currentFilters, userFilterConditions) returns the authored array unchanged when it is the only surviving source. Measured in a harness (18 rows, pagination.pageSize: 6, authored filter [["visible_from","is_not_null"],["due_date","is_not_null"]]): the paged request went out carrying that array verbatim.
                  • The gantt's own query goes through a compiler that ListView's does not.plugin-gantt/src/index.tsx declares OBJECT_GANTT_DATA_SOURCE = { filter: true, sort: true }, so ElementDataSourceGate (packages/react/src/element-data-source/ElementDataSourceGate.tsx) runs mergeFilterNodes(base.filter, composed.filter) before ObjectGantt ever reads schema.filter. mergeFilterNodes (packages/core/src/utils/filter-converter.ts) returns a lone surviving source as-is and wraps two or more as ["and", ...nodes] — with toFilterNode lowering any ViewFilterRule element to an AST node on the way through.
                  So the divergence is not random: it is one path composing and lowering where the other forwards. With a single filter source the two agree (my harness reproduced exactly that — both requests carried the flat authored array); with two or more surviving sources on the gantt side only, they part.
                  Why it is worth a card
                  1. The compilation is where a wrong answer could hide. Wrapping and operator lowering both change what the server matches if either side is imperfect. Nobody has checked that ["and", A, B] and [A, B] select the same rows through every adapter — @object-ui/data-objectstack maps is_not_null to isnotnull on the way out, and the two shapes reach that mapping through different amounts of normalization.
                  2. It makes the two requests hard to reason about as "the same rows twice." objectui#7210's half 3 is explicitly NOT "dedupe the requests", precisely because deduping means picking one of these dialects and picking wrong changes the result set silently. That decision cannot be taken until somebody has established the two are equivalent.
                  3. It is a divergence between siblings, not a property of one. Whatever the answer is, one authored filter should have one lowered form.
                  Suggested first step
                  Not a fix, a measurement: take an authored two-rule filter with two surviving sources, run both lowered shapes through ValueDataSource and through ObjectStackAdapter's serializer, and compare the row sets and the wire strings. If they agree, this is a tidiness card; if they do not, it is a correctness one and the severity moves.
                  Refs: objectui#7210 (parent observation, halves 2 and 3 still open there) · PR #7348 (the measurement pins) · #7349 (the correctness fix this card is blocked on).
                  Metadata
                  Metadata
                  Assignees
                  No one assigned
                    Labels
                    domain:uiobjectui ui stream: fix lands on the published library or apps — objectui execution seatpriority:p2
                    Type
                    No type
                    Projects
                    No projects
                      Milestone
                      No milestone
                      Relationships
                      None yet
                      Development
                      No branches or pull requests
                      Issue actions
                      
, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Auto-enable theater mode on YouTube\n(function() {\n function tryTheater() {\n var btn = document.querySelector('button[aria-label=\"Theater mode\"], ytd-player #player button[title=\"Theater mode\"]');\n if (btn && !btn.classList.contains('activated')) {\n btn.click();\n }\n }\n \n // Try immediately\n tryTheater();\n \n // Try after navigation (SPA)\n var lastUrl = location.href;\n setInterval(function() {\n if (location.href !== lastUrl) {\n lastUrl = location.href;\n setTimeout(tryTheater, 500);\n }\n }, 1000);\n \n // Also try on player load\n var observer = new MutationObserver(tryTheater);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "YouTube Theater Mode Default");
}
} catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

                      Skip to content
                      finding(plugin-gantt/plugin-list): one authored view filter reaches the wire in two dialects — ListView forwards it, the gantt path recompiles it through mergeFilterNodes #7221
                      Closed
                      Closed
                      finding(plugin-gantt/plugin-list): one authored view filter reaches the wire in two dialects — ListView forwards it, the gantt path recompiles it through mergeFilterNodes#7221
                      Labels
                      domain:uiobjectui ui stream: fix lands on the published library or apps — objectui execution seatpriority:p2
                      Description
                      @os-warren
                      os-warren
                      opened on Sep 1, 2026
                      Blocked-by: #7349
                      Recorded while implementing half 1 of objectui#7210. Filed separately because objectui#7210's ruling scoped the dialect disagreement OUT of that card: "if half 3's condition fails and both requests survive, the dialect mismatch is a finding to report, not to repair here." Half 3's condition did fail (the paged request has consumers other than the footer), so both requests survive and this needs its own home. Not a duplicate of objectui#7210 — that card is about the footer and the ceiling; this one is about the two shapes.
                      Filed unassigned, as an observation. I have not established that the two dialects ever select different rows; that is the first thing to measure and it is why this is worth a card rather than a note.
                      Measured 2026-09-02 (PR #7348, test-only pins): DIVERGENT. On the wire the two dialects are equivalent (the server lowers both to the same $and); through ValueDataSource they are not, because the in-memory matcher reads neither the flat implicit-AND array nor the null-ness operators. The correctness half is #7349; this card closes when the two it.fails cases named "diverges — objectui#7221" in packages/core/src/utils/__tests__/filter-dialect-equivalence-7221.test.ts flip to plain it there.
                      What the reporter saw
                      objectui#7210 measured one page load of a type: 'gantt' list view against published @objectstack/* 17.2.0 and got two requests whose filters do not agree:
                      paged filter=[["visible_from","is_not_null"],["due_date","is_not_null"]]
unbounded filter=["and",["visible_from","isnotnull",null],["due_date","isnotnull",null]]

                      Same authored view, same load, two wire shapes.
                      The two paths, read rather than assumed
                      • ListView's own query forwards the authored value.buildEffectiveFilter(schema.filter, currentFilters, userFilterConditions) returns the authored array unchanged when it is the only surviving source. Measured in a harness (18 rows, pagination.pageSize: 6, authored filter [["visible_from","is_not_null"],["due_date","is_not_null"]]): the paged request went out carrying that array verbatim.
                      • The gantt's own query goes through a compiler that ListView's does not.plugin-gantt/src/index.tsx declares OBJECT_GANTT_DATA_SOURCE = { filter: true, sort: true }, so ElementDataSourceGate (packages/react/src/element-data-source/ElementDataSourceGate.tsx) runs mergeFilterNodes(base.filter, composed.filter) before ObjectGantt ever reads schema.filter. mergeFilterNodes (packages/core/src/utils/filter-converter.ts) returns a lone surviving source as-is and wraps two or more as ["and", ...nodes] — with toFilterNode lowering any ViewFilterRule element to an AST node on the way through.
                      So the divergence is not random: it is one path composing and lowering where the other forwards. With a single filter source the two agree (my harness reproduced exactly that — both requests carried the flat authored array); with two or more surviving sources on the gantt side only, they part.
                      Why it is worth a card
                      1. The compilation is where a wrong answer could hide. Wrapping and operator lowering both change what the server matches if either side is imperfect. Nobody has checked that ["and", A, B] and [A, B] select the same rows through every adapter — @object-ui/data-objectstack maps is_not_null to isnotnull on the way out, and the two shapes reach that mapping through different amounts of normalization.
                      2. It makes the two requests hard to reason about as "the same rows twice." objectui#7210's half 3 is explicitly NOT "dedupe the requests", precisely because deduping means picking one of these dialects and picking wrong changes the result set silently. That decision cannot be taken until somebody has established the two are equivalent.
                      3. It is a divergence between siblings, not a property of one. Whatever the answer is, one authored filter should have one lowered form.
                      Suggested first step
                      Not a fix, a measurement: take an authored two-rule filter with two surviving sources, run both lowered shapes through ValueDataSource and through ObjectStackAdapter's serializer, and compare the row sets and the wire strings. If they agree, this is a tidiness card; if they do not, it is a correctness one and the severity moves.
                      Refs: objectui#7210 (parent observation, halves 2 and 3 still open there) · PR #7348 (the measurement pins) · #7349 (the correctness fix this card is blocked on).
                      Metadata
                      Metadata
                      Assignees
                      No one assigned
                        Labels
                        domain:uiobjectui ui stream: fix lands on the published library or apps — objectui execution seatpriority:p2
                        Type
                        No type
                        Projects
                        No projects
                          Milestone
                          No milestone
                          Relationships
                          None yet
                          Development
                          No branches or pull requests
                          Issue actions
                          
, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Remove or un-stick sticky/fixed headers that block content\n(function() {\n function unstick() {\n document.querySelectorAll('header, nav, [role=\"banner\"], .header, .navbar, .sticky, .fixed-top, [style*=\"position: fixed\"], [style*=\"position:sticky\"]').forEach(function(el) {\n if (el.style.position === 'fixed' || el.style.position === 'sticky' || \n getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {\n el.style.position = 'static';\n el.style.top = 'auto';\n el.style.zIndex = 'auto';\n }\n });\n }\n \n unstick();\n \n var observer = new MutationObserver(unstick);\n observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });\n})();", "Kill Sticky Headers");
}
} catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

                          Skip to content
                          finding(plugin-gantt/plugin-list): one authored view filter reaches the wire in two dialects — ListView forwards it, the gantt path recompiles it through mergeFilterNodes #7221
                          Closed
                          Closed
                          finding(plugin-gantt/plugin-list): one authored view filter reaches the wire in two dialects — ListView forwards it, the gantt path recompiles it through mergeFilterNodes#7221
                          Labels
                          domain:uiobjectui ui stream: fix lands on the published library or apps — objectui execution seatpriority:p2
                          Description
                          @os-warren
                          os-warren
                          opened on Sep 1, 2026
                          Blocked-by: #7349
                          Recorded while implementing half 1 of objectui#7210. Filed separately because objectui#7210's ruling scoped the dialect disagreement OUT of that card: "if half 3's condition fails and both requests survive, the dialect mismatch is a finding to report, not to repair here." Half 3's condition did fail (the paged request has consumers other than the footer), so both requests survive and this needs its own home. Not a duplicate of objectui#7210 — that card is about the footer and the ceiling; this one is about the two shapes.
                          Filed unassigned, as an observation. I have not established that the two dialects ever select different rows; that is the first thing to measure and it is why this is worth a card rather than a note.
                          Measured 2026-09-02 (PR #7348, test-only pins): DIVERGENT. On the wire the two dialects are equivalent (the server lowers both to the same $and); through ValueDataSource they are not, because the in-memory matcher reads neither the flat implicit-AND array nor the null-ness operators. The correctness half is #7349; this card closes when the two it.fails cases named "diverges — objectui#7221" in packages/core/src/utils/__tests__/filter-dialect-equivalence-7221.test.ts flip to plain it there.
                          What the reporter saw
                          objectui#7210 measured one page load of a type: 'gantt' list view against published @objectstack/* 17.2.0 and got two requests whose filters do not agree:
                          paged filter=[["visible_from","is_not_null"],["due_date","is_not_null"]]
unbounded filter=["and",["visible_from","isnotnull",null],["due_date","isnotnull",null]]

                          Same authored view, same load, two wire shapes.
                          The two paths, read rather than assumed
                          • ListView's own query forwards the authored value.buildEffectiveFilter(schema.filter, currentFilters, userFilterConditions) returns the authored array unchanged when it is the only surviving source. Measured in a harness (18 rows, pagination.pageSize: 6, authored filter [["visible_from","is_not_null"],["due_date","is_not_null"]]): the paged request went out carrying that array verbatim.
                          • The gantt's own query goes through a compiler that ListView's does not.plugin-gantt/src/index.tsx declares OBJECT_GANTT_DATA_SOURCE = { filter: true, sort: true }, so ElementDataSourceGate (packages/react/src/element-data-source/ElementDataSourceGate.tsx) runs mergeFilterNodes(base.filter, composed.filter) before ObjectGantt ever reads schema.filter. mergeFilterNodes (packages/core/src/utils/filter-converter.ts) returns a lone surviving source as-is and wraps two or more as ["and", ...nodes] — with toFilterNode lowering any ViewFilterRule element to an AST node on the way through.
                          So the divergence is not random: it is one path composing and lowering where the other forwards. With a single filter source the two agree (my harness reproduced exactly that — both requests carried the flat authored array); with two or more surviving sources on the gantt side only, they part.
                          Why it is worth a card
                          1. The compilation is where a wrong answer could hide. Wrapping and operator lowering both change what the server matches if either side is imperfect. Nobody has checked that ["and", A, B] and [A, B] select the same rows through every adapter — @object-ui/data-objectstack maps is_not_null to isnotnull on the way out, and the two shapes reach that mapping through different amounts of normalization.
                          2. It makes the two requests hard to reason about as "the same rows twice." objectui#7210's half 3 is explicitly NOT "dedupe the requests", precisely because deduping means picking one of these dialects and picking wrong changes the result set silently. That decision cannot be taken until somebody has established the two are equivalent.
                          3. It is a divergence between siblings, not a property of one. Whatever the answer is, one authored filter should have one lowered form.
                          Suggested first step
                          Not a fix, a measurement: take an authored two-rule filter with two surviving sources, run both lowered shapes through ValueDataSource and through ObjectStackAdapter's serializer, and compare the row sets and the wire strings. If they agree, this is a tidiness card; if they do not, it is a correctness one and the severity moves.
                          Refs: objectui#7210 (parent observation, halves 2 and 3 still open there) · PR #7348 (the measurement pins) · #7349 (the correctness fix this card is blocked on).
                          Metadata
                          Metadata
                          Assignees
                          No one assigned
                            Labels
                            domain:uiobjectui ui stream: fix lands on the published library or apps — objectui execution seatpriority:p2
                            Type
                            No type
                            Projects
                            No projects
                              Milestone
                              No milestone
                              Relationships
                              None yet
                              Development
                              No branches or pull requests
                              Issue actions
                              
, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Universal Dark Mode - works on any site\n(function() {\n var enabled = true;\n \n function applyDarkMode() {\n if (!enabled) return;\n \n // Create style element if it doesn't exist\n var style = document.getElementById('universal-dark-mode-style');\n if (!style) {\n style = document.createElement('style');\n style.id = 'universal-dark-mode-style';\n document.head.appendChild(style);\n }\n \n // Dark mode CSS - inverts colors but preserves images/video\n style.textContent = '\n /* Invert everything except media */\n html {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #1a1a2e !important;\n }\n \n /* Restore images, videos, iframes, canvas */\n img, video, iframe, canvas, svg, picture, [style*=\"background-image\"] {\n filter: invert(1) hue-rotate(180deg) !important;\n }\n \n /* Preserve specific elements that should not be inverted */\n .no-dark-mode, .no-dark-mode *,\n [data-theme=\"light\"], [data-theme=\"light\"],\n .ace_editor, .ace_editor *,\n .CodeMirror, .CodeMirror *,\n .monaco-editor, .monaco-editor *,\n .markdown-body pre, .markdown-body pre *,\n .highlight, .highlight *,\n pre code, pre code * {\n filter: none !important;\n }\n \n /* Fix common UI elements */\n .modal, .popup, .dropdown-menu, .tooltip, .popover {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #2d2d44 !important;\n border-color: #444 !important;\n }\n \n /* Scrollbars */\n ::-webkit-scrollbar { background: #1a1a2e !important; }\n ::-webkit-scrollbar-thumb { background: #444 !important; }\n ::-webkit-scrollbar-thumb:hover { background: #555 !important; }\n \n /* Selection */\n ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ';\n }\n \n function removeDarkMode() {\n var style = document.getElementById('universal-dark-mode-style');\n if (style) style.remove();\n }\n \n // Toggle with Alt+Shift+D\n document.addEventListener('keydown', function(e) {\n if (e.altKey && e.shiftKey && e.key === 'D') {\n e.preventDefault();\n enabled = !enabled;\n if (enabled) {\n applyDarkMode();\n console.log('[Universal Dark Mode] Enabled');\n } else {\n removeDarkMode();\n console.log('[Universal Dark Mode] Disabled');\n }\n }\n });\n \n // Apply on load\n applyDarkMode();\n \n // Re-apply on dynamic content\n var observer = new MutationObserver(function(mutations) {\n if (enabled && !document.getElementById('universal-dark-mode-style')) {\n applyDarkMode();\n }\n });\n observer.observe(document.head, { childList: true });\n \n console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');\n})();", "Universal Dark Mode");
}
} catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); }
})();
})();

                              Skip to content
                              finding(plugin-gantt/plugin-list): one authored view filter reaches the wire in two dialects — ListView forwards it, the gantt path recompiles it through mergeFilterNodes #7221
                              Closed
                              Closed
                              finding(plugin-gantt/plugin-list): one authored view filter reaches the wire in two dialects — ListView forwards it, the gantt path recompiles it through mergeFilterNodes#7221
                              Labels
                              domain:uiobjectui ui stream: fix lands on the published library or apps — objectui execution seatpriority:p2
                              Description
                              @os-warren
                              os-warren
                              opened on Sep 1, 2026
                              Blocked-by: #7349
                              Recorded while implementing half 1 of objectui#7210. Filed separately because objectui#7210's ruling scoped the dialect disagreement OUT of that card: "if half 3's condition fails and both requests survive, the dialect mismatch is a finding to report, not to repair here." Half 3's condition did fail (the paged request has consumers other than the footer), so both requests survive and this needs its own home. Not a duplicate of objectui#7210 — that card is about the footer and the ceiling; this one is about the two shapes.
                              Filed unassigned, as an observation. I have not established that the two dialects ever select different rows; that is the first thing to measure and it is why this is worth a card rather than a note.
                              Measured 2026-09-02 (PR #7348, test-only pins): DIVERGENT. On the wire the two dialects are equivalent (the server lowers both to the same $and); through ValueDataSource they are not, because the in-memory matcher reads neither the flat implicit-AND array nor the null-ness operators. The correctness half is #7349; this card closes when the two it.fails cases named "diverges — objectui#7221" in packages/core/src/utils/__tests__/filter-dialect-equivalence-7221.test.ts flip to plain it there.
                              What the reporter saw
                              objectui#7210 measured one page load of a type: 'gantt' list view against published @objectstack/* 17.2.0 and got two requests whose filters do not agree:
                              paged filter=[["visible_from","is_not_null"],["due_date","is_not_null"]]
unbounded filter=["and",["visible_from","isnotnull",null],["due_date","isnotnull",null]]

                              Same authored view, same load, two wire shapes.
                              The two paths, read rather than assumed
                              • ListView's own query forwards the authored value.buildEffectiveFilter(schema.filter, currentFilters, userFilterConditions) returns the authored array unchanged when it is the only surviving source. Measured in a harness (18 rows, pagination.pageSize: 6, authored filter [["visible_from","is_not_null"],["due_date","is_not_null"]]): the paged request went out carrying that array verbatim.
                              • The gantt's own query goes through a compiler that ListView's does not.plugin-gantt/src/index.tsx declares OBJECT_GANTT_DATA_SOURCE = { filter: true, sort: true }, so ElementDataSourceGate (packages/react/src/element-data-source/ElementDataSourceGate.tsx) runs mergeFilterNodes(base.filter, composed.filter) before ObjectGantt ever reads schema.filter. mergeFilterNodes (packages/core/src/utils/filter-converter.ts) returns a lone surviving source as-is and wraps two or more as ["and", ...nodes] — with toFilterNode lowering any ViewFilterRule element to an AST node on the way through.
                              So the divergence is not random: it is one path composing and lowering where the other forwards. With a single filter source the two agree (my harness reproduced exactly that — both requests carried the flat authored array); with two or more surviving sources on the gantt side only, they part.
                              Why it is worth a card
                              1. The compilation is where a wrong answer could hide. Wrapping and operator lowering both change what the server matches if either side is imperfect. Nobody has checked that ["and", A, B] and [A, B] select the same rows through every adapter — @object-ui/data-objectstack maps is_not_null to isnotnull on the way out, and the two shapes reach that mapping through different amounts of normalization.
                              2. It makes the two requests hard to reason about as "the same rows twice." objectui#7210's half 3 is explicitly NOT "dedupe the requests", precisely because deduping means picking one of these dialects and picking wrong changes the result set silently. That decision cannot be taken until somebody has established the two are equivalent.
                              3. It is a divergence between siblings, not a property of one. Whatever the answer is, one authored filter should have one lowered form.
                              Suggested first step
                              Not a fix, a measurement: take an authored two-rule filter with two surviving sources, run both lowered shapes through ValueDataSource and through ObjectStackAdapter's serializer, and compare the row sets and the wire strings. If they agree, this is a tidiness card; if they do not, it is a correctness one and the severity moves.
                              Refs: objectui#7210 (parent observation, halves 2 and 3 still open there) · PR #7348 (the measurement pins) · #7349 (the correctness fix this card is blocked on).
                              Metadata
                              Metadata
                              Assignees
                              No one assigned
                                Labels
                                domain:uiobjectui ui stream: fix lands on the published library or apps — objectui execution seatpriority:p2
                                Type
                                No type
                                Projects
                                No projects
                                  Milestone
                                  No milestone
                                  Relationships
                                  None yet
                                  Development
                                  No branches or pull requests
                                  Issue actions