I can confirm this in 4.5.4.

It's sort of related to repeating --- it basically seems like stuff in the non-repeated direction doesn't get clipped to the right thing --- when the background-origin is positive, it gets bounded by the padding box[1], and in the negative case... well, I am still trying to figure out what exactly it does then.

[1] The following CSS makes that case a bit clearer to see:
  <style type="text/css">
  div#outer
  {
  border: 1px solid blue;
  }

  div#inner
  {
  background-image: url("lime_color.png");
  background-position: 0px 5px; 
  background-repeat: repeat-x;
  border-top: transparent solid 100px;
  border-bottom: transparent solid 100px;
  width: 400px;
  height:10px;
  }
  </style>

Maksim,

Updated: http://www.gtalbot.org/BrowserBugsSection/Konqueror4Bugs/background-repeat-repeat-x.html

New: http://www.gtalbot.org/BrowserBugsSection/Konqueror4Bugs/background-repeat-repeat-x-2.html (inspired by your [1] code but a bit modified)

best wishes for the new year, Gérard

Maksim,

I have updated a bit
http://www.gtalbot.org/BrowserBugsSection/Konqueror4Bugs/background-repeat-repeat-x-2.html

Code is now:

  div#outer
  {
  border: blue solid 1px;
  width: 400px;
  }

  div#inner
  {
  background-image: url("../../GRAPHICS/PNG/lime_color.png");
  /* lime_color.png is a 100px wide by 100px tall image square */
  background-position: 0px 0px; 
  background-repeat: repeat-x;
  border-top: transparent solid 100px;
  border-bottom: transparent solid 100px;
  height: 1px;
  }

  <div id="outer">
    <div id="inner"></div>
  </div>

lime_color.png should be x-repeated 4 times and it should be viewable, visible through the transparent border-bottom.

regards, Gérard

! Better (for the testcase) is:

border-bottom: transparent solid 99px;

so that border-bottom (99px) + height (1px) == background-image's height (lime_color.png has a 100px height).

Gérard

Furthermore better (minimized) testcase:

http://www.gtalbot.org/BrowserBugsSection/Konqueror4Bugs/background-repeat-repeat-x-3.html

  div
  {
  background-image: url("../../GRAPHICS/PNG/lime_color.png");
  /* lime_color.png is a 100px wide by 100px tall image square */
  background-position: 0px 0px;
  background-repeat: repeat-x;
  border-bottom: transparent solid 100px;
  }
  </style>

  <p>Test passes if there is a bright green rectangle across the page.</p>

  <div></div>

Gérard

2 other testcases:

http://www.gtalbot.org/BrowserBugsSection/Konqueror4Bugs/background-repeat-repeat-x-4.html

With a (white) dotted border-bottom, the background-image should shine through between white dots. 
The second line shows a lime dotted border-bottom creating a reversed color scheme, like a chess board or reversi board.

http://www.gtalbot.org/BrowserBugsSection/Konqueror4Bugs/background-repeat-repeat-4.html
is the exact same testcase but this time with background-repeat set to repeat (not repeat-x) and Konqueror 4.5.5 handles such testcase as expected.

This bug is, I believe, a valid bug because
{
"background" refers to the background of the content, padding and border areas.
}
http://www.w3.org/TR/CSS21/colors.html#background
so even though background-position sets an initial (x, y) coordinates within the padding box, that does not mean that the background-color and background-image are not supposed to be under border areas (border-box).

regards, Gérard

I see something similar on the following pages

http://dixit.sourceforge.net/en/
or
http://dixit.sourceforge.net/en/shots.html

Interesting, the rendering is wrong ONLY IF one page is opened in
the browser. Once the second tab is added, the rendering is done
correctly in the first tab!!!!

Forgot to add:

Comments #8 and #9 happen for Konqueror 4.5.5 (KDE 4.5.5) on Fedora 14 KDE.

Dear user,

KHTML (and KJS) was a long time more or less unmaintained and got removed in KF6.

Please migrate to use a QWebEngine based HTML component.

We will do no further fixes or improvements to the KF5 branches of these components beside important security fixes.

For security issues, please see:

https://kde.org/info/security/

Sorry that we did not fix this issue during the life-time of KHTML.

Greetings
Christoph Cullmann