Avatar for Username

搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信，及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

Learn More

话题已存档。 如果需要帮助请提出新问题。

Resize issue with app (npapi plugin) embedded in firefox

  • 1 个回答
  • 6 人有此问题
  • 18 次查看
  • 最后回复者为 patrickmc

abhik
abhik
more options

Hi ,

issue:: When firefox is resized the embedded mfc application (which uses apapi plugin for embeddation) is unable to fit in the resize window(firefox).

NOTE:: Till 17.0 version the issue was not there , post 17.0 this issue is reproducible.

Some HINT:: whenever resized WM_PAINT (message 15 ) is send to application The code flow (pre 18.0 firefox version to embedded application):: 

     1)  pWnd->WindowProc(nMsg, wParam, lParam)

     2) CWnd::WindowProc ---> if (!OnWndMsg(message, wParam, lParam, &lResult))
		lResult = DefWindowProc(message, wParam, lParam);
                
     3) this in turn calls CView::OnPaint()

Now from 18.0, I am unable to get any call to my application.

Please help me out.

Let me know for further clarification

Thanks Abhi

Hi , issue:: When firefox is resized the embedded mfc application (which uses apapi plugin for embeddation) is unable to fit in the resize window(firefox). NOTE:: Till 17.0 version the issue was not there , post 17.0 this issue is reproducible. Some HINT:: whenever resized WM_PAINT (message 15 ) is send to application The code flow (pre 18.0 firefox version to embedded application):: <pre><nowiki> 1) pWnd->WindowProc(nMsg, wParam, lParam) 2) CWnd::WindowProc ---> if (!OnWndMsg(message, wParam, lParam, &lResult)) lResult = DefWindowProc(message, wParam, lParam); 3) this in turn calls CView::OnPaint() </nowiki></pre> Now from 18.0, I am unable to get any call to my application. Please help me out. Let me know for further clarification Thanks Abhi

由cor-el于修改

所有回复 (1)

patrickmc
patrickmc
more options

Hello Abhi,

I'm sorry that you're having issues with Firefox. Unfortunately, this is beyond the scope of assistance that we can give on SUMO.

I would suggest either creating a bug for this issue on Bugzilla against the Windows client or reaching out to the community at Stackoverflow.

They may have encountered this issue previously and have a workaround you can use.

Regards, Patrick