Gecko:Content Team Minutes: Difference between revisions

Jump to navigation Jump to search
m
fix brokenness of nested list markup
(mention nsObjectFrame)
m (fix brokenness of nested list markup)
Line 10: Line 10:
<ol>
<ol>
   <li>sicking: get XUL story in better shape, get somewhere with vector
   <li>sicking: get XUL story in better shape, get somewhere with vector
graphics.</li>
graphics.
   <ul>
   <ul>
     <li>brendan: beware w3c compound doc whim-wham, consider xul2 as
     <li>brendan: beware w3c compound doc whim-wham, consider xul2 as
Line 16: Line 16:
competitors. also, footprint, perf, web compatibility, etc.</li>
competitors. also, footprint, perf, web compatibility, etc.</li>
   </ul>
   </ul>
  </li>
   <li>[https://bugzilla.mozilla.org/show_bug.cgi?id=206531 wyciwyg caching for javascript:]
   <li>[https://bugzilla.mozilla.org/show_bug.cgi?id=206531 wyciwyg caching for javascript:]
   </li>
   </li>
Line 21: Line 22:
   </li>
   </li>
   <li>[https://bugzilla.mozilla.org/show_bug.cgi?id=274784 blazingly fast "Back" issues]
   <li>[https://bugzilla.mozilla.org/show_bug.cgi?id=274784 blazingly fast "Back" issues]
  </li>
   <ul>
   <ul>
     <li>can't just treat it like tab switching if
     <li>can't just treat it like tab switching if
onunload/onbeforeunload are missing, because of timers, blur handlers</li>
onunload/onbeforeunload are missing, because of timers, blur handlers</li>
   </ul>
   </ul>
  </li>
   <li>brendan, need help: [https://bugzilla.mozilla.org/show_bug.cgi?id=270553 E4X <-> DOM]
   <li>brendan, need help: [https://bugzilla.mozilla.org/show_bug.cgi?id=270553 E4X <-> DOM]
</li>
</li>
   <li>sicking: [https://bugzilla.mozilla.org/show_bug.cgi?id=240884 fix IndexOf quadratic growth]</li>
   <li>sicking: [https://bugzilla.mozilla.org/show_bug.cgi?id=240884 fix IndexOf quadratic growth]
   <ul>
   <ul>
     <li>sicking: will filling only in IndexOf pay off (don't want to
     <li>sicking: will filling only in IndexOf pay off (don't want to
fill in ChildAt)?</li>
fill in ChildAt)?</li>
     <li>bz: yes, for sibling following use-case</li>
     <li>bz: yes, for sibling following use-case</li>
     <li>jst: get something in, instrument cache hits/misses<br>
     <li>jst: get something in, instrument cache hits/misses</li>
    </li>
     <li>bz: fill for all kids (if above a threshold) on first IndexOf,
     <li>bz: fill for all kids (if above a threshold) on first IndexOf,
keep "search rotor" to start from<br>
keep "search rotor" to start from<br>
     </li>
     </li>
   </ul>
   </ul>
   <li>bz: extensibility story with XBL and XTF</li>
  </li>
   <li>bz: extensibility story with XBL and XTF
   <ul>
   <ul>
     <li>security story for these extension mechanisms</li>
     <li>security story for these extension mechanisms</li>
Line 86: Line 87:
     </li>
     </li>
   </ul>
   </ul>
   <li>dbaron: [https://bugzilla.mozilla.org/show_bug.cgi?id=283129 it's hard not to leak with our toolkit]</li>
  </li>
   <li>dbaron: [https://bugzilla.mozilla.org/show_bug.cgi?id=283129 it's hard not to leak with our toolkit]
   <ul>
   <ul>
     <li>brendan: maybe the ephemerality of XPConnect wrappers is the
     <li>brendan: maybe the ephemerality of XPConnect wrappers is the
Line 98: Line 100:
     <li>dbaron: sXBL and XBL2 fix this</li>
     <li>dbaron: sXBL and XBL2 fix this</li>
   </ul>
   </ul>
   <li>bz: native anonymous content:</li>
  </li>
   <li>bz: native anonymous content:
   <ul>
   <ul>
     <li>breaks some bindings, not scriptable</li>
     <li>breaks some bindings, not scriptable</li>
Line 105: Line 108:
     </li>
     </li>
   </ul>
   </ul>
   <li>better security model for XUL and XBL, broadly construed</li>
  </li>
   <li>better security model for XUL and XBL, broadly construed
   <ul>
   <ul>
     <li>brendan: work at higher level (data tainting?) with Coverity et
     <li>brendan: work at higher level (data tainting?) with Coverity et
Line 111: Line 115:
     <li>see Andrew Meyer's JIF?</li>
     <li>see Andrew Meyer's JIF?</li>
   </ul>
   </ul>
   <li>bz: display:none shouldn't tear down iframe content</li>
  </li>
   <li>bz: display:none shouldn't tear down iframe content
   <ul>
   <ul>
     <li>so we need to move docshell ownership into XBL</li>
     <li>so we need to move docshell ownership into XBL</li>
Line 124: Line 129:
     </li>
     </li>
   </ul>
   </ul>
  </li>
   <li>jst: plugins should be owned by content nodes, not frames
   <li>jst: plugins should be owned by content nodes, not frames
     <ul>
     <ul>
Line 132: Line 138:
more to do with mutation events, for code cleanup as well as perf.</li>
more to do with mutation events, for code cleanup as well as perf.</li>
   <li>brendan: are there high-level design changes to improve perf,
   <li>brendan: are there high-level design changes to improve perf,
not seen by profilers?</li>
not seen by profilers?
   <ul>
   <ul>
     <li>jst: batching of HTML content notifications is a mess, could be
     <li>jst: batching of HTML content notifications is a mess, could be
Line 147: Line 153:
sense</li>
sense</li>
   </ul>
   </ul>
  </li>
   <li>bz: document object setup and ownership (content viewer,
   <li>bz: document object setup and ownership (content viewer,
docshell, etc.)
docshell, etc.)
are hard to diagram</li>
are hard to diagram
   <ul>
   <ul>
     <li>brendan: draw "anatomical sections" or partial overlays</li>
     <li>brendan: draw "anatomical sections" or partial overlays</li>
Line 158: Line 165:
     </li>
     </li>
   </ul>
   </ul>
  </li>
   <li>bz: should we post wiki references to the m.dom etc. newsgroups?&nbsp;
   <li>bz: should we post wiki references to the m.dom etc. newsgroups?&nbsp;
group: Yes</li>
group: Yes</li>
   <li>jst: right before Firefox 1.0, we were fighting synthetic event
   <li>jst: right before Firefox 1.0, we were fighting synthetic event
bugs that got handled by chrome handlers; we could ignore those that
bugs that got handled by chrome handlers; we could ignore those that
aren't trusted events.</li>
aren't trusted events.
   <ul>
   <ul>
     <li>this breaks if we synthesize events that should be trusted but
     <li>this breaks if we synthesize events that should be trusted but
Line 169: Line 177:
     <li>Need a use-case.</li>
     <li>Need a use-case.</li>
   </ul>
   </ul>
  </li>
   <li>bz: event dispatch issues: two different methods on pres-shell to
   <li>bz: event dispatch issues: two different methods on pres-shell to
dispatch, one to content, one to content and to frames.</li>
dispatch, one to content, one to content and to frames.
   <ul>
   <ul>
     <li>Latter used from widget and view manager event sources, but
     <li>Latter used from widget and view manager event sources, but
Line 181: Line 190:
all (to content) if there are no frames.</li>
all (to content) if there are no frames.</li>
   </ul>
   </ul>
   <li>bryner, bz: dangling pointer to on-stack nsEvent bug</li>
  </li>
   <li>bryner, bz: dangling pointer to on-stack nsEvent bug
   <ul>
   <ul>
     <li>bryner, bz, hyatt: let's get rid of nsEvent stack allocation
     <li>bryner, bz, hyatt: let's get rid of nsEvent stack allocation
and all, and just move logic into DOM event classes.<br>
and all, and just move logic into DOM event classes.</li>
    </li>
     <li>bryner: some events have opaque pointers to native data not
     <li>bryner: some events have opaque pointers to native data not
valid after unwinding; need a method to null them out before unwinding</li>
valid after unwinding; need a method to null them out before unwinding</li>
Line 195: Line 204:
     </li>
     </li>
   </ul>
   </ul>
  </li>
   <li>Wiki URL: http://wiki.mozilla.org/wiki/Gecko:Content_Team_Minutes</li>
   <li>Wiki URL: http://wiki.mozilla.org/wiki/Gecko:Content_Team_Minutes</li>


</ol>
</ol>
/be
/be
canmove, Confirmed users, Bureaucrats and Sysops emeriti
1,334

edits

Navigation menu