Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. General and Desktop
  4. [SOLVED] QWebview frame resizing

[SOLVED] QWebview frame resizing

Scheduled Pinned Locked Moved General and Desktop
2 Posts 1 Posters 1.1k 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.
  • M Offline
    M Offline
    Moschops
    wrote on last edited by
    #1

    I have a QWebView that gets fed html pages to display. Some of these HTML pages have suddenly started using frames (let us party like it's 1999 :) ). When the html file is viewed in a standard browser, the frame is resizeable (i.e. dragable, left to right - it's a single frame, splitting the page vertically in two). In the QWebView widget, it is not. This is bad.

    It does have a horizontal scrollbar at the bottom of the left frame, so a user can scroll to see everything, and expanding/shrinking the entire QWebView seems to alter the size of the two frames proportionately. It's like in the QWebView, the frames are fixed proportions, but in a standard browser, they are not (kind of - in Opera, the frame boundary is visible and draggable, in Firefox it's invisible but still draggable, and in the QWebView it's invisible and not draggable).

    Is there some setting I'm missing to enable the frame boundary to be dragged in the QWebView, or is this some limitation of the QWebView (or even some issue with the html page, and the test browser is smoothing over some edges that the simpler QWeb View doesn't?)?

    Edit: I speak no HTML. I understand that the <frameset> section of the source concerns this sort of thing. Is it possible that there's something in that being interpreted one way by the browser (i.e. allow resizing) and another way by the QWebView? There is also a css file which does contain the word "framebox", so maybe that's involved too :(

    1 Reply Last reply
    0
    • M Offline
      M Offline
      Moschops
      wrote on last edited by
      #2

      Just for closure, I'm pretty sure it turned out to be this bug:

      https://bugs.webkit.org/show_bug.cgi?id=23750

      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