Closed Bug 14611 Opened 21 years ago Closed 21 years ago
[BLOCKER] Can't select non-text nodes such as HR, IMG, and table elements
We used to be able to click on a HR or Image to select it. That doesn't work any more. If you can't select an image, you can't bring up the property dialog for that image, thus it blocks work on editing properties of an image. Tables are a problem. While I understand that people complained about not being able to select text in tables, we need to be able to select table cells in both the browser and editor.
the portion about hr and image is critical for beta. If it's an easy, safe fix, please try to get it in for M11. Otherwise, M12.
*** Bug 14821 has been marked as a duplicate of this bug. ***
I thought I put comments in here earlier today but apparently not. The workaround for this bug should be to place the caret immediately before or after the image/hrule you want to select and then use the shift and arrow to select it. (Though this is far from obvious.) Unfortunately the selection seems to disappear. Also, no dialog comes up at all for hrule (an empty image dlog comes up for an image). Has anyone reported this problem? This happens on Mac as well so changing platform/OS to ALL.
I don't think your "workaround" sets the same selection as clicking on the object used to. Thus when you try to run a property dialog, GetSelectedElement() fails because it is very fussy about having just the object in question selected. HRules will be inserted instead of property editing in this case, other dialogs will not show the settings of the intended object. MIKE: ARE YOU FIXING THIS SOON PLEASE?
Mike, please look at this today. If it can be fixed safely, it should go in for M10, which pretty much means today sometime.
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
this is fixed. i thought i updated the bug sorry
okay you can select it all right but now we have another problem in that you can't un-select it so you can type text next to the object...I filed another bug...
You need to log in before you can comment on or make changes to this bug.