This is NOT about size. The component and its bounding box are separate… often. This happens when I save a thing, then go back and reopen it to work on it again. The box will be totally separate from the actual component things, often off in the distance. I cannot “select” anything either in the actual component, or in the remote bounding box… it just acts like a click in space that deselects it. I can do a Cmd-A to select all, and I see them both. Until I do that, if I click on the actual component, it acts like nothing is there.
yes. it happens when you save while a group or component is open.
select it, press enter to open the component, then exit it. it should be fixed.
1 Like
Thank you… I should have given more details. I am using the on-line version, on a MacBook. I do cmd-a to select it. then I see what is in the picture. Hitting “Return” does nothing. I try to get the pointer to click on a thing, and nothing “opens” the component. I can get Scale and Move to work… but that isn’t opening the component.
well that bug is exclusively in the web version 
and selecting the element, pressing enter (or return, same thing) then escape is the current solution…
you need to select only THE problematic group or component, if you do cmd-a you’ll select everything. and you can’t open everything at once (therefore pressing enter doesn’t do anything)
1 Like
Ok, thank you. I will experiment… and most importantly, I now know how not to create this situation. Thank you sooooo much!!
AHA! It was those stupid measurements. I thought I put them IN the component, but I did not! Thanks
1 Like
the usual suspect, the stupid measurement 
a fix seems to be on the way, but until then, you know the trick
I’m a bit late to the party but Aaron posted this video a couple of weeks ago which explains a lot of issues with bounding boxes.
I know you’ve got the issue sorted but it’s still worth taking just over 10 minutes to watch it.
Thanks. I like those types of videos, because I often spy a subtle but helpful keyboard trick or something like that, beyond just the thing you are investigating
2 Likes
I have an update about this problem…
Once we had ways to reproduce the issue, which could only be caused in the web version and iPad, we did do a fix to stop it happening again. But, that didn’t take care of models that already had the problem.
We now have added a fix that repairs groups and components that have the problem already. That fix just went live. If you reopen any affected model, in the web version of SketchUp, the bounding boxes should now be ok.
The same fix isn’t on iPad yet, but will be there in the next update. In the meantime, if you see the problem on iPad, open the web version and load your model, and do a save. Then it should be fixed in the iPad app as well. This works even in Safari on iPad, no need to involve a computer or Chrome on iPad.
The fix also isn’t in desktop yet, so models shared from web or iPad may still show the issue. On desktop it’s easier to repair the group by opening it to edit, then closing it again. The next desktop update will have the fix in it. Meantime, the opening and saving in web would fix the model for desktop as well.
1 Like