If you open an article in the browser (pressing 'o' on the reader screen), the browser instance is run as a child of the bulletty process. This can be tested by closing bulletty: the browser closes as well. The only time this doesn't happen is when there is a browser instance already running with other tabs open; in that case, the article tab is indeed forked, but I guess that's due to the browser.
Expected behavior: if an article is opened from bulletty in the browser, the browser instance should be forked such that closing bulletty does not close it.
If you open an article in the browser (pressing 'o' on the reader screen), the browser instance is run as a child of the bulletty process. This can be tested by closing bulletty: the browser closes as well. The only time this doesn't happen is when there is a browser instance already running with other tabs open; in that case, the article tab is indeed forked, but I guess that's due to the browser.
Expected behavior: if an article is opened from bulletty in the browser, the browser instance should be forked such that closing bulletty does not close it.