Fresh
unread,May 13, 2024, 5:15:49 PM5/13/24Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Chromium Extensions, Oliver Dunk, Chromium Extensions, Pavel Aronovich, Fresh
Thanks, I appreciate the technical explanation. It makes sense, and I get that extensions are incredibly difficult to distribute without presenting serious security risks to the end user, so they have to be implemented strictly. For that I am glad there is still an option to distribute a self hosted extension at all.
That said I strongly agree about the documentation. If the restrictions are going to be so strict they should be well explained, little caveats like this and all. The current documentation has most of this done very well, but I think my experience with this is a good example of a pain point that could be polished. Stuff that might be logical for an experienced developer, but docs are often read by people who are new to framework they're working in.
On topic of the original question, the ForceInstall policy worked and we've been able to test the extension on our systems for deployment. The biggest hurdle was indeed in our misunderstanding of how we were 'supposed' to be able to locally test whether the extension install policy was working. It also didn't help that when searching the issue online, it seemed like the 'rules' for self hosted extensions seemed to change a lot over time, so many answers were outdated as, like you said, the requirements are constantly evolving. For a good reason, but it just makes it more difficult as a developer to keep track of what's 'correct' which definitely needs to be offset with crystal clear docs.
But, yes, thank you, this has helped me understand the whole process much better, and I'm just glad it works and wasn't as complicated (if finnicky) as I thought.