Been over 3 weeks since I looked at this and tried to duplicate the bug using comment 0 steps. It didn't fail. Then I recalled that the steps in comment 0 has an error. Here are the correct steps: 1. Connect successfully to nntp news group. 2. Simulate a network failure by dropping incoming data from port 119/nntp: ```sudo iptables -A INPUT -p tcp --sport nntp -j DROP``` 3. Click on a message. Of course, message does not appear. 4. Switch TB to offline 5. Remove the drop rule (fixes the simulated error): ```sudo iptables -D INPUT -p tcp --sport nntp -j DROP``` 6. Switch TB to online 7. Click on another message not the same as step 3 message. Message header and body comes in. 8. Click again on step 3 message. Body displays as blank, header from step 7 remains displayed. (In reply to Magnus Melin [:mkmelin] from comment #16) > (In reply to gene smith from comment #15) > > I think it would be better just to pop up an error message like other protocols do that doesn't take over the whole message area. > > I think we do want to show the error page instead of a dialog, where possible, as that's much nicer and less disruptive UI. Of course when moving to next msg, any actions for the previous message should get disregarded. 1859522 I just found that the ```about:neterror``` pages were something you fairly recently added to JS nntp implementation at bug 1859522. I tried 91 again and it unreliably/sometimes also puts up the about:neterror page, and the "Try again" button is a noop at 91 too (running c++ implementation). I have no clue how to make the "Try again" button work so I'll file a new bug for that. Note: With the "Try again" button working, the only way to try again is move to another message and then back to the original original failed message. But if there is only one message (would be pretty unusual I think) the only way to try it again is to open it in a new window or tab.
Bug 1876261 Comment 18 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Been over 3 weeks since I looked at this and tried to duplicate the bug using comment 0 steps. It didn't fail. Then I recalled that the steps in comment 0 has an error. Here are the correct steps: 1. Connect successfully to nntp news group. 2. Simulate a network failure by dropping incoming data from port 119/nntp: ```sudo iptables -A INPUT -p tcp --sport nntp -j DROP``` 3. Click on a message. Of course, message does not appear. 4. Switch TB to offline 5. Remove the drop rule (fixes the simulated error): ```sudo iptables -D INPUT -p tcp --sport nntp -j DROP``` 6. Switch TB to online 7. Click on another message not the same as step 3 message. Message header and body comes in. 8. Click again on step 3 message. Body displays as blank, header from step 7 remains displayed. (In reply to Magnus Melin [:mkmelin] from comment #16) > (In reply to gene smith from comment #15) > > I think it would be better just to pop up an error message like other protocols do that doesn't take over the whole message area. > > I think we do want to show the error page instead of a dialog, where possible, as that's much nicer and less disruptive UI. Of course when moving to next msg, any actions for the previous message should get disregarded. 1859522 I just found that the ```about:neterror``` pages were something you fairly recently added to JS nntp implementation at bug 1859522. I tried 91 again and it unreliably/sometimes also puts up the about:neterror page, and the "Try again" button is a noop at 91 too (running c++ implementation). I have no clue how to make the "Try again" button work so I'll file a new bug for that. Note: With the "Try again" button *NOT* working, the only way to try again is move to another message and then back to the original original failed message. But if there is only one message (would be pretty unusual I think) the only way to try it again is to open it in a new window or tab.
Been over 3 weeks since I looked at this and tried to duplicate the bug using comment 0 steps. It didn't fail. Then I recalled that the steps in comment 0 has an error. Here are the correct steps: 1. Connect successfully to nntp news group. 2. Simulate a network failure by dropping incoming data from port 119/nntp: ```sudo iptables -A INPUT -p tcp --sport nntp -j DROP``` 3. Click on a message. Of course, message does not appear. Maybe select a few more messages which won't appear 4. Switch TB to offline (simulates resetting network hardware) 5. Remove the drop rule (fixes the simulated error): ```sudo iptables -D INPUT -p tcp --sport nntp -j DROP``` 6. Switch TB to online (this could be done after step 4 with same results) 7. Click on another message not the same as step 3 message(s). Message header and body comes in. 8. Click again on step 3 message(s). Body(s) displays as blank, header from step 7 remains displayed. (In reply to Magnus Melin [:mkmelin] from comment #16) > (In reply to gene smith from comment #15) > > I think it would be better just to pop up an error message like other protocols do that doesn't take over the whole message area. > > I think we do want to show the error page instead of a dialog, where possible, as that's much nicer and less disruptive UI. Of course when moving to next msg, any actions for the previous message should get disregarded. 1859522 I just found that the ```about:neterror``` pages were something you fairly recently added to JS nntp implementation at bug 1859522. I tried 91 again and it unreliably/sometimes also puts up the about:neterror page, and the "Try again" button is a noop at 91 too (running c++ implementation). I have no clue how to make the "Try again" button work so I'll file a new bug for that. Note: With the "Try again" button *NOT* working, the only way to try again is move to another message and then back to the original original failed message. But if there is only one message (would be pretty unusual I think) the only way to try it again is to open it in a new window or tab.
Been over 3 weeks since I looked at this and tried to duplicate the bug using comment 0 steps. It didn't fail. Then I recalled that the steps in comment 0 has an error. Here are the correct steps: 0. Setup a news (NNTP) group and configure so that no offline storage is used so server is accessed on first read of every article in steps below. 1. Connect successfully to nntp news group. 2. Simulate a network failure by dropping incoming data from port 119/nntp: ```sudo iptables -A INPUT -p tcp --sport nntp -j DROP``` 3. Click on a message. Of course, message does not appear. Maybe select a few more messages which won't appear 4. Switch TB to offline (simulates resetting network hardware) 5. Remove the drop rule (fixes the simulated error): ```sudo iptables -D INPUT -p tcp --sport nntp -j DROP``` 6. Switch TB to online (this could be done after step 4 with same results) 7. Click on another message not the same as step 3 message(s). Message header and body comes in. 8. Click again on step 3 message(s). Body(s) displays as blank, header from step 7 remains displayed. (In reply to Magnus Melin [:mkmelin] from comment #16) > (In reply to gene smith from comment #15) > > I think it would be better just to pop up an error message like other protocols do that doesn't take over the whole message area. > > I think we do want to show the error page instead of a dialog, where possible, as that's much nicer and less disruptive UI. Of course when moving to next msg, any actions for the previous message should get disregarded. 1859522 I just found that the ```about:neterror``` pages were something you fairly recently added to JS nntp implementation at bug 1859522. I tried 91 again and it unreliably/sometimes also puts up the about:neterror page, and the "Try again" button is a noop at 91 too (running c++ implementation). I have no clue how to make the "Try again" button work so I'll file a new bug for that. Note: With the "Try again" button *NOT* working, the only way to try again is move to another message and then back to the original original failed message. But if there is only one message (would be pretty unusual I think) the only way to try it again is to open it in a new window or tab.