+++ This bug was initially created as a clone of Bug #72591 +++ Bug 72591 was regressed in bug 80494, despite the fact that the patch there didn't have review.
> despite the fact that the patch there didn't have review. This is factually incorrect, the patch had an r+. Anyway, we can certainly discuss this again. However, we'll need a strong reason to consider removing this long-standing feature. In addition to compatibility constraints, there is evidence that developers want it - e.g. jQuery implements document.width/height for engines that don't have it. As an aside, I'm puzzled by the influx of bugs asking us to remove things that are in latest official specs or used to be more widely implemented, while not seeing any bugs asking us to remove truly WebKit-specific extensions to DOM.
(In reply to comment #1) > As an aside, I'm puzzled by the influx of bugs asking us to remove things that are in latest official specs or used to be more widely implemented, while not seeing any bugs asking us to remove truly WebKit-specific extensions to DOM. Would you accept patches for such bugs? If so, I'd be very happy to file them.
Removing purely WebKit extensions is less controversial than removing things that are in current W3C specs. Each suggestion would need to be judged on its own merits, and I obviously cannot guarantee that all or any of these would result in code changes.
Note that document.width/height aren't in any spec, btw.
Correct. This has been extensively discussed in bug 72591.
Both of these return undefined for me. This must have gotten fixed at some point. (We still have Document::width() and Document::height(), but presumably those are for app compatibility as discussed in the various bugs.)