Skip to content

Open any url not assigned to a container in the default container#63

Merged
kintesh merged 3 commits intokintesh:masterfrom
Nepherte:master
Jul 8, 2019
Merged

Open any url not assigned to a container in the default container#63
kintesh merged 3 commits intokintesh:masterfrom
Nepherte:master

Conversation

@Nepherte
Copy link

@Nepherte Nepherte commented Jun 9, 2019

This change only keeps urls explicitly assigned to a container into that container. Urls not assigned to a container will be opened into the default one (ie. 'No Container'). As such, assigning urls to 'No Container' no longer makes sense and has been removed.

@Nepherte
Copy link
Author

Nepherte commented Jun 9, 2019

Also related to #10.

@doronbehar
Copy link

Thanks @Nepherte, I've checked out your PR and I'm the happiest Container user ever! Since @kintesh is not responsive, and due to the fact he seem to ignore his users' honest requests as for this small but significant behavior change, very much like in #20, I think you should fork this addon and publish it at Mozilla's addon gallery by your self. I'd would have done so my self but I think the honor should be yours.

@kintesh kintesh merged commit bf51832 into kintesh:master Jul 8, 2019
@doronbehar
Copy link

Thanks @kintesh , I'm sorry I've doubted your concern to your users. I can't wait to see a new release and stop use my personal fork. Thanks a lot for creating this extension in the first place :).

@kintesh
Copy link
Owner

kintesh commented Jul 8, 2019

Sorry dude. I had to find some time been very busy moving home and stuff.

kintesh added a commit that referenced this pull request Jul 9, 2019
…ssigned to a container in the default container Commit: bf51832 [bf51832]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

Comments