I'm not clear on what happens wrt inline v. block on these slots.  it seems like the outer will often need to be inline, but if it's always inline, won't that cause problems in IE?  Can we create a new html tag for it?  <nest> or something?  would that solve anything?

---

much more useful to have examples on test.dwagn.org.

  --Ethan McCutchen.....Tue Dec 14 09:57:24 -0800 2010

---

I'm not sure the solution above will work. The outer slot must be either a block element or an inline element, no? I think most browsers will choose one or the other, even if we make it a tag, but that merits exploration. Anyway, either will potentially create issues. we should do some serious browser testing before we do any coding.

  --Ethan McCutchen.....Tue Dec 14 10:05:35 -0800 2010

---

is refactor inclusion processing part of this?

  --John Abbe.....Sat Jan 22 15:17:27 -0800 2011

---

not really. what we're doing is definitely a refactor of the slot apparatus underneath, but this is talking about generating different html and handling it differently, which we're not doing.

  --Ethan McCutchen.....Sat Jan 22 15:26:11 -0800 2011

---

took browser screenshots: http://crossbrowsertesting.com/users/ethan/screenshots/43168/57483

  --Ethan McCutchen.....Thu Mar 10 16:23:23 -0800 2011

---

"Access denied. You may need to login below or register to access this page."

  --John Abbe.....Fri Mar 11 16:17:05 -0800 2011

---

http://crossbrowsertesting.com/users/26675/screenshots/zaf704171a8cc59f7b69/public

  --Ethan McCutchen.....Fri Mar 11 16:20:42 -0800 2011