I got an issue logged on SQL Developer's Facebook page.
As I can't see this bug ID on My Oracle Support, I'd like to ask here, what the status of it is. Will it be fixed in 4.0?
They're still both open bugs. We have a ways to go before 4.0 will be officially released. Stay tuned.