See [
^] for a good discussion of event-bubbling and UserControl inheritance in ASP.NET. And: [
^].
For "up event bubbling" in JavaScript, see: [
^].
When you create an
instance of a UserControl, the UserControl instance is a dynamic entity based on its code definition: it doesn't quite make sense to say that the UserControl "inherits" its code definition, just as you wouldn't say a building "inherits" its blueprints.
If you create a UserControl definition, and then create another UserControl definition that inherits from it, you might imagine this as being one set of blueprints that uses/references another set of blueprints.
I suggest you ask your instructor for clarification of what they mean by using "event bubbling" in this assignment: ask if they mean something more than just having Event Handlers defined in some containing entity that holds the log-in dialog.