Class GraphicsConfiguration

java.lang.Object
vaadinx.awt.GraphicsConfiguration

public final class GraphicsConfiguration extends Object
Import-swap target for GraphicsConfiguration — the browser viewport's single display configuration (D_graphics_environment). Reached the JDK way, through the environment and its default device:
GraphicsConfiguration gc = GraphicsEnvironment.getLocalGraphicsEnvironment()
        .getDefaultScreenDevice().getDefaultConfiguration();
Rectangle screen = gc.getBounds();   // (0, 0, viewportWidth, viewportHeight)

Like Toolkit this does not extend the abstract JDK class — it is the import-swap surface, not a platform configuration — so getDevice() returns the vaadinx device rather than the JDK's (R_no_vaadin_in_api limb 1). There is exactly one instance, GraphicsDevice.getDefaultConfiguration(): a browser has one viewport.

Bounds track the live viewport through BrowserToolkitInfo, so a value read before a browser resize goes stale — re-read rather than caching.

The image-creation and capability bodies are the JDK's own, which are pure raster maths and run correctly headless. Only the VolatileImage family is dropped: it needs a real accelerated surface, which a server JVM has not got.