Closed Bug 92460 Opened 24 years ago Closed 24 years ago

TestGtkEmbed missing scroll bars and key based scroll

Categories

(Core Graveyard :: Embedding: APIs, defect, P1)

Product:
Core Graveyard
Component:
Embedding: APIs
Platform:
x86
Linux
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED DUPLICATE of bug 90707

People

(Reporter: tracy, Assigned: blizzard)

Details

(Keywords: smoketest)

seen on TestGtkEmbed 2001-07-26-06-trunk just launch the app... there aren't any scroll bars and the keyboard scrolling functions are inactive also.
Keywords: smoketest
adam is on vacation until early august, maybe blizzard can look at this?
I've seen this before. It's usually a packaging problem.
-> blizzard@mozilla.org
Assignee: adamlock → blizzard
This works in my local opt build fine. What are you using?
we just added TestGtkEmbed to the packaging file, I probably didn't know to add something that TestGtkEmbed needs. Tracey downloads the tar.gz file from mozilla.org.
after respin we need to test and verify this one
Priority: -- → P1
Which tar.gz file? Tell me which file specifically.
OK, I can reproduce that problem with the build that you pointed me at but it's working fine in my local build that has symbols.
This is broken in 2001-07-25-06-trunk, too. When did this work? Is this a new bug?
Hyatt, where do the scrollbars come from? I see that scrollbars.css is in the embed.jar file: 3223 06-13-01 17:32 skin/clasic/global/scrollbars.css And there's an entry in all-packages.rdf: <RDF:Description about="urn:mozilla:package:global" c:baseURL="jar:resource:/chrome/embed.jar!/content/global/" c:locType="install" c:displayName="Toolkit" c:author="mozilla.org" c:name="global" c:localeVersion="0.9.3" c:skinVersion="1" /> Does this look OK to you?
I'm removing the blocker status on this. I don't think that it's ever worked properly.
Severity: blocker → critical
So can someone tell me the steps to generate the embed.tar.gz so that I can build it locally with debugging symbols? I would really appreciate it.
afaik: make -C embedding/config then tar up the dist/Embed dir
When I do that from a fresh tree I get some warnings: Warning: package error or possible missing or unnecessary file: chrome/embed.jar (./basebrowser-unix, 241). Warning: package error or possible missing or unnecessary file: chrome/pipnss.ja r (./basebrowser-unix, 169). Warning: package error or possible missing or unnecessary file: chrome/pippki.ja r (./basebrowser-unix, 172).
somehow we use embedding/config/basebrowser-unix to do the packaging, leaf does this, maybe he can chime in here.
this looks like a dup, mfcembed also has this problem. *** This bug has been marked as a duplicate of 90707 ***
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
verified dupe
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.