![]() ![]() Currently nested intercepts doesn't seem to work for me.Preserve scroll of the page while the intercept slot is shown (modal in my case) I saw on Twitter that this was actively being worked on, so I'm looking forward to it in a future update.Overall I'm glad that is now possible natively without super hacky code. ![]() I was able to get a basic version of a "either open in modal or separate page based on current route" interaction. /app/middleware/session-factory.ts import How those extra children are OK? □ cc Was this translation helpful? Give feedback. Things inserted when rendering the shell~ are inserted into and I'm not sure what kind of rule makes this OK here since that's bypassing React. I'm also a little bit confused when it comes to useServerInsertedHTML. cc I agree that a lot of things can break the reconciliation - a custom container used as root was always a good enough boundary that allowed 3rd party things to work most of the time. Perhaps the issue reporters could shed some more light on what they are trying to achieve there to get some advice here. I only got a minimal repro that had this in the extension:ĭ(document.createElement('foo')) I'm not exactly sure what the real extension was trying to do. The root cause behind this that I've diagnosed is the same thing that is being discussed here - rehydrating the whole. I got a bug report for Emotion recently that showcased to me how a Remix app gets broken with somebody's web extension. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |