| 17:26 | <mgaudet> | ljharb: What's your planned direction for Error.stacks? I'm trying to prep for our agenda review and a lack of slides has me wondering what's changed |
| 17:27 | <ljharb> | nothing’s changed with the proposal. I’m hoping that the “boil the ocean” requirement won’t still exist |
| 17:34 | <mgaudet> | So reading the notes (I can't find old slides here) it doesn't seem like much has meaningfully changed? Like I'm not saying that it's in good shape, but I'm curious about what you plan on presenting |
| 17:34 | <mgaudet> | *It being here "the state of Error stacks" |
| 17:36 | <mgaudet> | We have a real webcompat problem around Errors that I have volunteered to try and look into (https://bugzilla.mozilla.org/show_bug.cgi?id=1886820) and it's definitely related to this and we may need to do something absolutely funky which ends up aligning things |
| 17:37 | <mgaudet> | This actually bakes -more- of the web platform onto the opposite side of what you've got speced now, which is Error.prototype.stack |
| 17:50 | <ljharb> | nothing has changed, yes. the intention of the proposal is to specify the schema/structure, and not the contents |
| 17:51 | <ljharb> | i'd love an issue filed that talks more about the compat issue. i'm not that familiar with captureStackTrace since the plan was always to get it removed entirely |
| 17:59 | <mgaudet> | Unfortunately that ship may have sailed when WebKit shipped it https://github.com/WebKit/WebKit/commit/997e074bb35ed07b69c9b821141c91dd548e0d02 |
| 18:03 | <mgaudet> | Issue opened for you https://github.com/tc39/proposal-error-stacks/issues/48 |