Bug 4286 - Failure to open URL correctly
Summary: Failure to open URL correctly
Status: RESOLVED INVALID
Alias: None
Product: Claws Mail (GTK 2)
Classification: Unclassified
Component: Plugins/Dillo-Viewer (show other bugs)
Version: 3.17.4
Hardware: PC FreeBSD
: P3 normal
Assignee: users
URL:
Depends on:
Blocks:
 
Reported: 2019-12-18 11:02 UTC by Gerard Seibert
Modified: 2019-12-18 11:34 UTC (History)
0 users

See Also:

Attachments
What happens when I attempt to click on a link in an email. (59.44 KB, image/png)
2019-12-18 11:30 UTC, Gerard Seibert 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Description Gerard Seibert 2019-12-18 11:02:51 UTC 

    


    


      



        
          Comment 1
        

        
          Paul

        

        
        

        
          2019-12-18 11:05:27 UTC
        

      






closing as INVALID as this bug report contains no useful information

    


    


      



        
          Comment 2
        

        
          Gerard Seibert

        

        
        

        
          2019-12-18 11:30:17 UTC
        

      






Created attachment 2032 [details]
What happens when I attempt to click on a link in an email.

When I click on a link in an email, a warning box pops up. I am unable to actually reach the URL. The URL is displayed as shown in this image: <https://www.seibercom.net/logs/Screen-1.png>. Now, if the URL was simply displayed like the one I just posted, then that site would open in the web browser.

This is the system info:

Operating System: FreeBSD 11.3
KDE Plasma Version: 5.17.4
KDE Frameworks Version: 5.64.0
Qt Version: 5.13.2
Kernel Version: 11.3-RELEASE-p5
OS Type: 64-bit
Processors: 4 × ACPI CPU
Memory: 31.7 GiB of RAM

    


    


      



        
          Comment 3
        

        
          Paul

        

        
        

        
          2019-12-18 11:34:51 UTC
        

      






That's a bug in dillo, not a bug in claws-mail.

    



  






  


    

      

        

          
            

              Note
              You need to
              log in
              before you can comment on or make changes to this bug.