Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. QtWebEngine
  4. Qt 5.6 WebEngine problem with custom FlashPLayer locations
Forum Updated to NodeBB v4.3 + New Features

Qt 5.6 WebEngine problem with custom FlashPLayer locations

Scheduled Pinned Locked Moved Unsolved QtWebEngine
3 Posts 1 Posters 2.0k Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • T Offline
    T Offline
    ThatDud3
    wrote on last edited by
    #1

    According to Qt 5.6 › Qt WebEngine › Qt WebEngine Platform Notes › Adobe Flash Player Plugin Support (section) :

    You can also load the Flash player from a specific location by using command line arguments:

    --ppapi-flash-path=./libpepflashplayer.so
    

    ...but it is not working.

    Suggestion in the first paragraph works though:
    "The Adobe Flash player plugin can be loaded automatically if it is installed in one of the following locations, depending on the platform:"
    If I copy to default path (that is also searched by WebEngine it works...

    I mean using custom path works if I do it from command line too like:

    app.exe --ppapi-flash-path=./pepflashplayer.dll
    

    but it is not working when I do it in code like:

    QApplication a(argc, my_argv);
    qDebug() << "my_argv: " << qApp->arguments(); // ("C:\\temp\\app.exe", "--ppapi-flash-path=./pepflashplayer.dll") 
    

    so my_argv should be passed down to WebEngine but not honored
    Is this a known bug in WebEngine...

    1 Reply Last reply
    0
    • T Offline
      T Offline
      ThatDud3
      wrote on last edited by
      #2

      I've found a few similar bugs but they are all fixed...
      https://bugreports.qt.io/browse/QTBUG-30330
      https://bugreports.qt.io/browse/QTBUG-47023
      https://codereview.qt-project.org/#/c/105750/

      The only possibility left is that Chromuim doesn't use QApplication's argv and relies on arguments retrieved by GetCommandLine()
      My question is - is this a bug or it is by design and what is the point of having qApp->arguments() if they aren't passed to QWebEngine?

      1 Reply Last reply
      0
      • T Offline
        T Offline
        ThatDud3
        wrote on last edited by
        #3

        I opened a bug report QTBUG-51971

        1 Reply Last reply
        0

        • Login

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • Users
        • Groups
        • Search
        • Get Qt Extensions
        • Unsolved