That sounds pretty much exactly in line with how I'd like to see this
code evolve. It seems like FrameLoader should hold the following
state:
1) The various DocumentLoaders (provisional, policy, and committed).
2) A state machine concerning the lifecycle of navigating a frame
(displaying initial
I have an idea for a rule of thumb for what code should be in FrameLoader and
what should go in DocumentLoader.
I’d suggest that we leave code in frame loader that relates to switching from
one document to the next. Starting a navigation to a new location, creating a
document loader for the new
2 matches
Mail list logo
