New support channel for XUL extension development Topic is solved
Moderators: FranklinDM, Lootyhoof
Re: New support channel for XUL extension development
I wish I could but the documents already seem purged. Why aren't you linking what you are removing cause now the thing doesn't even 404 just goes to unhelpful search.
- RealityRipple
- Astronaut
- Posts: 662
- Joined: 2018-05-17, 02:34
- Location: Los Berros Canyon, California
- Contact:
Re: New support channel for XUL extension development
The first two haven't been removed; the last two still exist on MDN. I put them back for now (with links to mdn's message manager page since that was in the now-deleted multiprocess_firefox folder).
https://udn.realityripple.com/docs/Web/API/FileRequest
https://udn.realityripple.com/docs/Web/API/HTMLIFrameElement/setNFCFocus
https://udn.realityripple.com/docs/Archive/Mozilla/XUL/Attribute/remote
https://udn.realityripple.com/docs/Archive/Mozilla/XUL/Property/messageManager
https://udn.realityripple.com/docs/Web/API/FileRequest
https://udn.realityripple.com/docs/Web/API/HTMLIFrameElement/setNFCFocus
https://udn.realityripple.com/docs/Archive/Mozilla/XUL/Attribute/remote
https://udn.realityripple.com/docs/Archive/Mozilla/XUL/Property/messageManager
- RealityRipple
- Astronaut
- Posts: 662
- Joined: 2018-05-17, 02:34
- Location: Los Berros Canyon, California
- Contact:
Re: New support channel for XUL extension development
I was planning on adding Mozilla/Tech/XPCOM/Reference/Interface/nsISyncMessageSender, nsIContentFrameMessageManager, nsIMessageSender, nsIMessageListener, and nsIMessageBroadcaster to the list, but nsIMessageManager.idl is still part of UXP, so... now I'm confused about the whole multiprocess thing. Should I be getting rid of docs on multiprocess stuff or is it still a usable part of UXP?
Re: New support channel for XUL extension development
eMatrix uses nsIMessageListenerManager and nsIMessageSender (at least), so I'd appreciate if you didn't remove them.
- RealityRipple
- Astronaut
- Posts: 662
- Joined: 2018-05-17, 02:34
- Location: Los Berros Canyon, California
- Contact:
Re: New support channel for XUL extension development
So the message system is functional in UXP? I guess I can just have their links to the Multiprocess_Firefox folder point to the official MDN site instead...
Re: New support channel for XUL extension development
You never know when they get rid of that in their zeal to rip out everything from the past, or if that section changes in response to changes with their codebase. Why not just retain it as a snapshot of multiprocess in Firefox as it was back then? At this point I am glad for your backup as a stable alternative to the original, some of which still exists and the rest 404s.RealityRipple wrote: ↑2021-03-11, 22:17I guess I can just have their links to the Multiprocess_Firefox folder point to the official MDN site instead...
"One hosts to look them up, one DNS to find them and in the darkness BIND them."
Linux Mint 21 Xfce x64 on HP i5-5200 laptop, 12 GB RAM.
AutoPageColor|PermissionsPlus|PMPlayer|Pure URL|RecordRewind|TextFX
Linux Mint 21 Xfce x64 on HP i5-5200 laptop, 12 GB RAM.
AutoPageColor|PermissionsPlus|PMPlayer|Pure URL|RecordRewind|TextFX
- RealityRipple
- Astronaut
- Posts: 662
- Joined: 2018-05-17, 02:34
- Location: Los Berros Canyon, California
- Contact:
Re: New support channel for XUL extension development
I don't want to retain anything that's not in Goanna. If it turns out I need to retain the Message_Manager subsection, I'll move it to another folder, but I'm pretty sure the rest of the stuff in Multiprocess_Firefox is in the "not in Goanna" category.
Re: New support channel for XUL extension development
You should probably check the codebase with e.g. the xref, before you remove pages linking to XPCOM interfaces, even if it looks "not Goanna".
Re: New support channel for XUL extension development
You can always just fix the links but otherwise leave it as it is.. A backup of important info that has no replacement yet.
Re: New support channel for XUL extension development
Yes, fixing the links within articles would be good.
"One hosts to look them up, one DNS to find them and in the darkness BIND them."
Linux Mint 21 Xfce x64 on HP i5-5200 laptop, 12 GB RAM.
AutoPageColor|PermissionsPlus|PMPlayer|Pure URL|RecordRewind|TextFX
Linux Mint 21 Xfce x64 on HP i5-5200 laptop, 12 GB RAM.
AutoPageColor|PermissionsPlus|PMPlayer|Pure URL|RecordRewind|TextFX
- RealityRipple
- Astronaut
- Posts: 662
- Joined: 2018-05-17, 02:34
- Location: Los Berros Canyon, California
- Contact:
Re: New support channel for XUL extension development
As I said earlier, I'm trying to reduce the workload on fixing things by reducing the number of pages I have to deal with a bit. 18,000 is a lot.
I'm moving Message_Manager (and Types_of_message_manager) to the /Mozilla/Gecko/ directory. If any other sections of "Multiprocess_Firefox" are found to be required later, I'll put them in better locations. However, I'm pretty sure none of them apply to UXP/Goanna:
/
/Cross_Process_Object_Wrappers
/Debugging_frame_scripts
/FAQ
/Frame_script_environment
/Glossary
/Limitations_of_chrome_scripts
/Limitations_of_frame_scripts
/Motivation
/Pitfalls_for_add-on_developers
/RemotePageManager
/Tab_selection_in_multiprocess_Firefox
/Technical_overview
/Web_content_compatibility
/Which_URIs_load_where
I'm moving Message_Manager (and Types_of_message_manager) to the /Mozilla/Gecko/ directory. If any other sections of "Multiprocess_Firefox" are found to be required later, I'll put them in better locations. However, I'm pretty sure none of them apply to UXP/Goanna:
/
/Cross_Process_Object_Wrappers
/Debugging_frame_scripts
/FAQ
/Frame_script_environment
/Glossary
/Limitations_of_chrome_scripts
/Limitations_of_frame_scripts
/Motivation
/Pitfalls_for_add-on_developers
/RemotePageManager
/Tab_selection_in_multiprocess_Firefox
/Technical_overview
/Web_content_compatibility
/Which_URIs_load_where
Re: New support channel for XUL extension development
Again because of eMatrix, having the 2nd, 5th, 7th and 8th page, even in a different location, would be useful.
Maybe I won't use it, but if I'll ever have to hand maintenance of that extension to someone else, I'd appreciate if those pages would be available for reference.
Maybe I won't use it, but if I'll ever have to hand maintenance of that extension to someone else, I'd appreciate if those pages would be available for reference.
- RealityRipple
- Astronaut
- Posts: 662
- Joined: 2018-05-17, 02:34
- Location: Los Berros Canyon, California
- Contact:
Re: New support channel for XUL extension development
Understood. CPOWs, Frame Script Environment, and the two Limitations pages will be retained. I'm putting it all into a "Multiprocess_Leftovers" folder and throwing the message system in there, too.
- RealityRipple
- Astronaut
- Posts: 662
- Joined: 2018-05-17, 02:34
- Location: Los Berros Canyon, California
- Contact:
Re: New support channel for XUL extension development
Due to major power issues, I won't be able to work on this (or any other project) for the next week or so. Sorry for the delay in repairing bad links and adding Prism to script examples, but it's gonna be a while before I can do anything.
Re: New support channel for XUL extension development
Not a problem. Hope it wasn't too severe like massive dataloss or something.
- RealityRipple
- Astronaut
- Posts: 662
- Joined: 2018-05-17, 02:34
- Location: Los Berros Canyon, California
- Contact:
Re: New support channel for XUL extension development
No. My whole house is off-grid, and the system is... not working.
Re: New support channel for XUL extension development
Ah. Well I hope you get it sorted soon.
Re: New support channel for XUL extension development
You really saved the day. Most of links about outdated contents on MDN no longer work now.
- RealityRipple
- Astronaut
- Posts: 662
- Joined: 2018-05-17, 02:34
- Location: Los Berros Canyon, California
- Contact:
Re: New support channel for XUL extension development
Please redirect all further discussion about UDN to the designated topic.