DW9 quits when adding Spry Menu elements

Using version 9.0 build 3481 on a Mac G5 tower (2@ 2GHz). I
inserted a Spry Menu Bar (vertical). Adding the first few items
went smoothly, but now when I add any items, DW "unexpectantly
quits." I've posted the work so far
HERE.
Tried repairing permissions and clearing out machine caches,
but still crashes.
Any suggestions??
Thanks,
rob

Found my answer the next morning...
In the properties panel, click the button marked "Turn Styles
Off".

Similar Messages

Error when adding any menu - FRM-40735: ON-INSERT trigger raised unhandled

When I try to add any new menu in my newly cloned instance I get this error:
Error when adding any menu - FRM-40735: ON-INSERT trigger raised unhandled excpetion. ORA-04031.
Using Oracle EBS version 12.1.3.
Details:
Menu JOB_STRUCTURE_MENU
User Menu Name Job Strucure Menu
Menu Type Standard
Description Menu to add job, grade, and incentives
Seq = 1
Prompt = Enter and Maintain
Function = Combined Person & Assignment Form WF="US SHRMS TSKFLW
When I click save I get the error.
Any assistance would be greatly appreciated.
Thanks!

Please post the details of the application release, database version and OS.
When I try to add any new menu in my newly cloned instance I get this error:
Error when adding any menu - FRM-40735: ON-INSERT trigger raised unhandled excpetion. ORA-04031.Is the issue with all menus or specific ones only?
Did AutoConfig complete successfully?
When I click save I get the error.
Any assistance would be greatly appreciated.Do you have any invalid objects in the database?
Any errors in the database log file?
Please obtain FRD log file for details about the error -- https://forums.oracle.com/forums/search.jspa?threadID=&q=FRD+AND+R12&objID=c3&dateRange=all&userID=&numResults=15&rankBy=10001
Thanks,
Hussein

IMovie quits when adding titles

iMovie (9.0.8) quits when adding titles (and sometimes just randomly although it seems to be related to adding titles).
I have repaired permissions and deleted com.apple.iMovieApp.plist from library to no avail.
It is not related to a corrupt project as it happens to all my current projects.
This is the first part of the crash report:
Process:         iMovie [16194]
Path:            /Applications/iMovie.app/Contents/MacOS/iMovie
Identifier:      com.apple.iMovieApp
Version:         9.0.8 (1778)
Build Info:      iMovieApp-1778000000000000~1
Code Type:       X86 (Native)
Parent Process: launchd [148]
User ID:         501
Date/Time:       2012-10-21 10:49:22.738 +0800
OS Version:      Mac OS X 10.8.2 (12C60)
Report Version: 10
Interval Since Last Report:          316922 sec
Crashes Since Last Report:           21480
Per-App Interval Since Last Report: 216105 sec
Per-App Crashes Since Last Report:   7
Anonymous UUID:                      41763BF4-5BD1-26E5-4614-F60738A1FE56
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x000000000000025d
VM Regions Near 0x25d:
--> __PAGEZERO             0000000000000000-0000000000001000 [    4K] ---/--- SM=NUL /Applications/iMovie.app/Contents/MacOS/iMovie
    VM_ALLOCATE            0000000000001000-00000000000e2000 [ 900K] ---/--- SM=NUL

Hi
I doubt - BUG - I guess corrupted iMovie pref file (to get this You only need to Force/Panic Halt the program and errors are entered in it)
See if this helps
When iMovie doesn't work as intended this can be due to a lot of reasons
• iMovie Pref files got corrupted - trash it/they and iMovie makes new and error free one's
• Creating a new User-Account and log into this - forces iMovie to create all pref. files new and error free
• Event or Project got corrupted - try to make a copy and repair
• a codec is used that doesn't work
• problem in iMovie Cache folder - trash Cache.mov and Cache.plist
• version miss match of QuickTime Player / iMovie / iDVD
• preferences are wrong - Repair Preferences
• other hard disk problem - Repair Hard Disk (Disk Util tool - but start Mac from ext HD or DVD)
• External hard disks - MUST BE - Mac OS Extended (hfs) formatted to work with Video
( UNIX/DOS/FAT32/Mac OS Exchange - works for most other things - but not for Video )
• USB-flash-memories do not work
• Net-work connected hard disks - do not work
• iPhoto Library got problems - let iPhoto select another one or repair it. Re-build this first then try to re-start iMovie.
This You do by
_ close iPhoto
_ on start up of iPhoto - Keep {cmd and alt-keys down}
_ now select all five options presented
_ WAIT a long long time
• free space on Start-Up (Mac OS) hard disk to low (<1Gb) - I never go under 25Gb free space for SD-Video (4-5 times more for HD)
• external devices interferes - turn off Mac - disconnect all of them and - Start up again and re-try
• GarageBand fix - start GB - play a few notes - Close it again and now try iMovie
• Screen must be set to million-colors
• Third-party plug-ins doesn't work OK
• Run "Cache Out X", clear out all caches and restarts the Mac
• Let Your Mac be turned on during one night. At about midnight there is a set of maintenance programs that runs and tidying up. This might help
• Turn off Your Mac - and disconnect Mains - for about 20-30 minutes - at least this resets the FireWire port.
• In QuickTime - DivX, 3ivx codec, Flip4Mac, Perian etc - might be problematic - temporarily move them out and re-try
(I deleted the file "3ivxVideoCodec.component" located in Mac HD/Library/Quicktime and this resolved my issue.)
buenrodri wrote
I solved the problem by removing the file: 3ivxVideoCodec.component. after that, up-dated iMovie runs ok.
Last resort: Trash all of iMovie and re-install it
Yours Bengt W

Added Spry menu in CS3, site is entirely blank in IE 6 or 7, fine in FF, mac

I've about had it. Built a site, posted here with some issues
with a P7 menu adding blue bar. I deleted all the P7 code...page
was back to normal, but without a navigation bar. So, I added one
of the new Spry bars in DW, set it all up, tested it on my Mac,
works fine.
I upload all pages to server, open it in Explorer 6 and 7 on
PC, and I get one blank white page! I downloaded Firefox for PC,
and the site is fine there. It's fine everywhere else. At first, I
had just the background tile in IE. Didn't panic yet. Did some
stuff, and then even that is gone.
I can not comprehend where to begin troubleshooting this. I
did not backup the site before I started screwing with this, so I'm
in trouble here.
the url is
http://www.auroratownship.org/proto
Do you guys see a plain white page too? If you have Firefox
or another browser, can you try it there as well to see what it is
supposed to look like? I even tried deleting all the Spry menu
stuff, didn't matter.
HELP!

So far I've not spotted the problem for usre, but there is
one
validation error that you should fix, just in case.
<noscript>
<map>
Menu provided by f-source.com, All Rights Reserved. <a
href="
http://f-source.com">Web
menu</a>
</map>
</noscript>
remove that errant <map></map> tag and see what
happens.
E. Michael Brandt
www.divaHTML.com
divaGPS | divaFAQ
www.valleywebdesigns.com
JustSo PictureWindow
synterx wrote:
> I've about had it. Built a site, posted here with some
issues with a P7 menu
> adding blue bar. I deleted all the P7 code...page was
back to normal, but
> without a navigation bar. So, I added one of the new
Spry bars in DW, set it
> all up, tested it on my Mac, works fine.
>
> I upload all pages to server, open it in Explorer 6 and
7 on PC, and I get one
> blank white page! I downloaded Firefox for PC, and the
site is fine there. It's
> fine everywhere else. At first, I had just the
background tile in IE. Didn't
> panic yet. Did some stuff, and then even that is gone.
>
> I can not comprehend where to begin troubleshooting
this. I did not backup the
> site before I started screwing with this, so I'm in
trouble here.
>
> the url is
http://www.auroratownship.org/proto
>
> Do you guys see a plain white page too? If you have
Firefox or another
> browser, can you try it there as well to see what it is
supposed to look like?
> I even tried deleting all the Spry menu stuff, didn't
matter.
>
> HELP!
>

Javascript error when selecting Spry Menu Bar in Design View

Hi there,
I get the following error message when trying to format the Spry Menu Bar in Design View:
"while executing inspectSelection in spry_menu.htm, a Javascript error occurred."
I have tried the following troubleshooting steps:
deleting site cache
closing/re-opening Dreamweaver
deleting Spry Menu Bar and recreating - same error occurs.
Other information:
I am using a MacBook Pro
it happens when clicking on the Menu Bar itself. I just want to change the properties
the Spry Menu Bar does not appear in Live View.
Here is a link to my site on Browserlab. It has not yet been published:
https://browserlab.adobe.com/en-us/index.html#zoom=100;state=use;view=0;url=dreamweaver%3A %2F%2Fsite%3AHope%2520Against%2520Hope%2FHAH_home.html;browsers=WXPIE6000%2CWXPIE9000%2COS XFF7000%2COSXSF5000%2CWXPCH14000
Is it a case of changing one of the values in the spry_menubar.js file?
Can anyone help?
Thanks,
Charlie

Hi there,
The problem appears to have returned. I am getting the same error message as before and also an error saying there is a syntax error in my source code. Dreamweaver tells me which line the error is in:
var MenuBar1 = new Spry.Widget.MenuBar("hope_menu", {imgDown:"SpryAssets/SpryMenuBarDownHover.gif", imgRight:"SpryAssets/SpryMenuBarRightHover.gif"});
In response to your earlier questions/points:
I am using version 0.13 of SpryMenuBar.js (is this what you mean?)
The menu now shows in Live View as I would expect it to
Here is a link to my published site:
http://hopeagainsthopeuk.co.uk/HAH_home.html
Do you have any further advice?

Error when adding Spry Tooltip to page with footer library

I'm using Dreamweaver CS4 and the Spry menu to apply widgets.
I was able to create a brand new page, import an image, and apply the Spry Tooltip widget successfully (as well as edit the CSS etc.).
But I run into problems when I applied it to an image on my real page, which is pretty busy, and in columns etc. I select the same image and apply the Spry Tooltip. I get this error message:
"Making this change would require changing code that is locked by a template or a translator. The change will be discarded."
Searching online, it seemed to have something to do with a region that is not editable, like a template or library item. I'm not using Templates, but I did have a few library items. The Library for my footer, which included the script for Google Analytics, was what was causing the problems.
It seems what Tooltip was trying to do was insert its script INSIDE the existing script in the Footer library - which is not editable. I needed to remove the Footer Library, apply the tooltip, then re-insert the Footer Library. This is how it needed to flow:
</div>

<div id="footer">
<p>footer copy here</p>
</div>
<script type="text/javascript">
blah blah google analytics stuff...
</script>

<div class="tooltipContent" id="sprytooltip1">Tooltip content here.</div>
<script type="text/javascript">

</script>
</body>
</html>
I think if the footer library didn't have a script in it, it would not have been an issue. It's just that the </script> was right before the </body> and it figured it could just insert the Spry code there.
I wasted an hour troubleshooting this - I wish Dreamweaver was smarter when it inserted widgets and would know where Library items started and stopped.

Select your external drive in finder.
press CMD and i
an info windows will open - what is reported as "Format" ?
anyway scroll down to the very bottom: "Sharing & Permissions"
set everyone's privilege to "Read & Write" and choose to "Apply to all enclosed items"

Premiere elements crashing when adding disc menu on a mac

This has been happening for quite some time now.
I have tried saving as flv and mpg to avoid the problem but it still crashes.
Is there a solution. I am running OSX 10.9.2
I have verified the disk and permissions to no avail.
I have a project that I need to finish.

Thank you for your response
What exactly is happening and when?
When I have finished editing the movie and ready to add a disc menu so that it can be played on DVD. Disc Menu is selected and when I try to drag it across the error occurs and it shuts down the program
Movie Menus only apply if you are creating a DVD, a BluRay or a WebDVD. Why are you outputting as an MPEG and FLV? I output as an MPEG and FLV to add to the internet and to keep as files for future use.
What model of camcorder is your original footage coming from and what format and resolution is it? I am importing an mov file which I have made a slideshow from in Slideshow Pro. I have been using the same process for over a year and it has only started happening in about 4 months ago.
When you add your video to your timeline in Timeline mode, do you see a red line alone the top of the timeline, above the clips? This indicates that you did not properly set up your project to match your video. No red line
What are your Project Properties, as listed under the Edit menu?
It might also help to know the hardware specs of your computer.
MacBook Pro -
Processor 2.9 GHz Intel Core i7
Memory 8 GB 1600 MHz DDR3
Graphics Intel HD Graphics 4000 1024 MB
Software OS X 10.9.2 (13C64)

Mail quit when adding an exchange account

I can't configure an exchange account on 10.9.4, Mail quit everytime.
Same thing when using the internet account system preference.
A message appears about a sub-window preference problem.
I've added this account on 10.8.4 and on my iPad without any problem.

Mail.app crashes while setting up an Exchange Account

ITunes quits when adding to library

I have a MacBook and am running iTunes 7.6.2. I have a smaller library already on my MacBook, consisting of about 6 gigs of music. I am trying to import my larger library from my PC, consisting of about 31 gigs of music, onto the MacBook. I can't simply replace the library, because the MacBook has some songs that aren't on the PC. I use iTunes to automatically sort my playlists.
After transferring the music files to the MacBook, I selected "Add to Library" and selected the music. iTunes started to re-copy the files into the Library already there, after which I would just delete the originals that I transferred over. Unfortunately, every time I attempt to do this, iTunes just quits unexpectedly during the process. I've tried all the usual tricks, including deleting the library file, the com.apple.Itunes.plist file, the XML file, and starting over. If I attempt to use iTunes after attempting to import the music, it acts unstable and randomly quits. The only way I can restore it is to use Time Machine to restore back to the old, smaller 6 gig library.
I have the crash report from one of the attempts, although it's different each time. Here's the crashed thread:
Thread 8 Crashed:
0 libSystem.B.dylib 0xffff1250 __longcopy + 80
1 libSystem.B.dylib 0xffff086e __memcpy + 206
2 com.apple.iTunes 0x001ddd7d 0x1000 + 1953149
3 com.apple.iTunes 0x001fc4c8 0x1000 + 2077896
4 com.apple.iTunes 0x000f464c 0x1000 + 996940
5 com.apple.iTunes 0x001759e3 0x1000 + 1526243
6 com.apple.iTunes 0x00176af3 0x1000 + 1530611
7 com.apple.iTunes 0x000edd8f 0x1000 + 970127
8 com.apple.iTunes 0x000ee1d3 0x1000 + 971219
9 com.apple.iTunes 0x001114b5 0x1000 + 1115317
10 com.apple.iTunes 0x0027c910 0x1000 + 2603280
11 ...ple.CoreServices.CarbonCore 0x9346fe1d CooperativeThread + 309
12 libSystem.B.dylib 0x9478b6f5 pthreadstart + 321
13 libSystem.B.dylib 0x9478b5b2 thread_start + 34
Thread 8 crashed with X86 Thread State (32-bit):
eax: 0x00000000 ebx: 0x00000000 ecx: 0x01c1c5d9 edx: 0x00040000
edi: 0x18885000 esi: 0x1ad1e5a9 ebp: 0xb01bcaac esp: 0xb01bcaa0
ss: 0x0000001f efl: 0x00010246 eip: 0xffff1250 cs: 0x00000017
ds: 0x0000001f es: 0x0000001f fs: 0x0000001f gs: 0x00000037
cr2: 0x1ad1e5a9
And I looked at the com.apple.iTunes.plist file after the crash, and it appears to be mostly nothing but thousands of capital "A's" with a few scattered characters throughout.
Any insight into how I can successfully consolidate my two libraries would be greatly appreciated. Thanks!

Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
The title of the Console window should be All Messages. If it isn't, select
SYSTEM LOG QUERIES ▹ All Messages
from the log list on the left. If you don't see that list, select
View ▹ Show Log List
from the menu bar at the top of the screen. Click the Clear Display icon in the toolbar. Then take one of the actions that you're having trouble with. Select any messages that appear in the Console window. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.
The log contains a vast amount of information, almost all of which is irrelevant to solving any particular problem. When posting a log extract, be selective. A few dozen lines are almost always more than enough.
Please don't indiscriminately dump thousands of lines from the log into this discussion.
Please don't post screenshots of log messages—post the text.
Some private information, such as your name, may appear in the log. Anonymize before posting.

Update mac to maverick system shuts down when adding disc menu

I recently updated my mac to Maverick and now when I add my disc menu my system shutdown after stating a serious error occurred.
How can I fix this problem

sweetboo5
This current thread represents a duplicate of the original
http://forums.adobe.com/message/6150140#6150140
A moderator is expected to be along shortly to close the thread we are in now.
Please see your other thread cited above for further exchange of comments.
Thanks.
ATR

Spry Menu 1.6.1 vs Spry Menu 2.0 (1.7) aka UI Menubar

I have been working with the original Spry Menu that came with CS5 for some time now. Slowly I have been learning how to use it, and more importantly, edit it without breaking it. There are some great articles out there by David Power that I printed out and keep in a folder at my desk. Great stuff.
Now I want to build a menu that is supported on touch pads like an iPad. Having spent many hours trying to figure it all out, I found a post that said you had to use the Spry Menu 2.0 version for touch features. Oops, did not know that. Having upgraded to the new version in the Widget Browser, customized it for colors and such, I put into a test page. This is where it went all wrong.
I have no access to anything in the Properties Selector area. It’s just blank, no options at. If I go back to one of my old menus, it works just fine. So I can't add top or submenu items to the menu like I could in the old version, unless I want to type out the code. The menu does not display is design view like a finished product. All I get is a listing of the menu. I have to display the page in a browser or in live view mode to see it display right. Which throws the page all out whack and it’s hard to edit with this big long list of text.
So, I guess my question here is. Does this sound right to everyone? I saw a posting by Gramps, which makes me think I understand the problem above it true and because of that he sticks to the original version. I want the touch pad access so I need to upgrade.
Is there a fix I have not found? Some code change to make it all happy again? Should I just dump the idea of using the Spry Menu and use something else?
Thanks to everyone out there who take the time to answer our questions. I think this is a my very first posting.

Amy, welcome to our fold.
You have struck the epitome of the problem when using Spry Menu 2.0, it is a beast when one tries to shape and style it outside of the Widget Browser. The markup looks very meek and mild as in
<ul id="MenuBar">
<li> <a href="#">Home</a></li>
<li> <a href="#">Entertainment</a></li>
<li> <a href="#">Politics</a></li>
<li> <a href="#">Sports</li>
</ul>
but once it is interpreted by the JavaScript, it looks like
<div class="MenuBar MenuBarLeftShrink" id="MenuBar">
    <ul id="" class="MenuBarView">
    <li class="MenuItemContainer"><a href="#" class="MenuItem MenuItemFirst" tabindex="0"><span class="MenuItemLabel">Home</span></a></li>
    <li class="MenuItemContainer"><a href="#" class="MenuItem" tabindex="-1"><span class="MenuItemLabel">Entertainment</span></a></li>
    <li class="MenuItemContainer"><a href="#" class="MenuItem" tabindex="-1"><span class="MenuItemLabel">Politics</span></a></li>
    <li class="MenuItemContainer"><a href="#" class="MenuItem" tabindex="-1"><span class="MenuItemLabel">Sports</span></a></li>
    <a href="#" class="MenuItem" tabindex="-1"><span class="MenuItemLabel MenuItemLast"></span></a>
</ul><br class="MenuBarBreak">
</div>
<a href="#">

</a>
</body>
</html>
There are certain aspects that I do not understand without spending time to follow them through. There is no documentation so you are left on your own. When submenu levels are added, the generated markup looks even stranger.
The main problem with the original SpryMenuBar is its lack of support for touch screens; alternatively one could say that the problem lies with touch screens and their lack of ability to register hover events.
This means that if we had a menubar that is not reliant upon hover events, our menubar will work in touch screen clients. In our menu above (that is the one that has not been reformed by JS), there is no hover event. All of the menuitems, being single level, follow the link with a click event. It is when a menuitem has a link as well as submenus that a hover event is required. If we remove the link when a menuitem has submenus, we also remove the need for a hover event and it will work in touch screen devices. To illustrate this
<ul id="MenuBar1" class="MenuBarHorizontal">
<li><a class="MenuBarItemSubmenu" href="#">Item 1</a> 
    <ul>
      <li><a href="mylink11.html">Item 1.1</a></li>
      <li><a href="mylink12.html">Item 1.2</a></li>
      <li><a href="mylink13.html">Item 1.3</a></li>
    </ul>
</li>
<li><a href="mylink2.html">Item 2</a></li>
<li><a class="MenuBarItemSubmenu" href="#">Item 3</a> 
    <ul>
      <li><a class="MenuBarItemSubmenu" href="#">Item 3.1</a> 
        <ul>
          <li><a href="mylink311.html">Item 3.1.1</a></li>
          <li><a href="mylink312.html">Item 3.1.2</a></li>
        </ul>
      </li>
      <li><a href="mylink32.html">Item 3.2</a></li>
      <li><a href="mylink33.html">Item 3.3</a></li>
    </ul>
</li>
<li><a href="mylink4.html">Item 4</a></li>
</ul>
There are commercial extensions available that do work within DW as opposed to products from the Widget Browser that do not allow for DW interaction.
Gramps

Spry Menu being covered by embedded video

I embedded a video on my homepage, but when my spry menu flys out to the right, the submenus are covered by the video. Shouldn't the video be under the submenus since it's part of my page's DIV? If the DIV that the video is in had text, that text would be behind the submenus, but that's not the case for the video. what am I missing?

This helped me!
wmode="transparent" was the answer in my case.
Thank you.

Spry menu bar won't update when published

I am building a dreamweaver webpage though a template.
for some reason it will not change the spry menu bar to update the changes made to the links on it.
that and the links won't work on the website (i uploaded it to a test website).
I am not sure if it is the same problem.
I changed the links from site to document relative.
I also checked the codes in http://validator.w3.org/check and http://jigsaw.w3.org/css-validator/ .
I also read this link and it didn't help me http://helpx.adobe.com/dreamweaver/kb/paths-dreamweaver-templates.html .
Can someone help please!
Thank you

I am not sure why that will not upload to the site correctly.
I am uploading to a godaddy server. Is there a way I should be saving things (links and such) that I might be doing wrong? am I naming my links incorrectly? how do I make them so they will work once uploaded.
I followed the suggestions that you made and it looks like it is there but for somereason when i preview the page in a browser or live view the background image (parchment) doesn't show up on the screen.and the spry menu bar only comes up as an unordered list. I am not sure what would be causing this.
I have attached the code for 2 pages the first is the code of the template test file you suggested I make and the second is the code for the education connection page (this is a page that was made from the template and the background image is not working-i had this problem before but i thought it was fixed as the website has it fixed when i published it)
TEST SITE:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />

<title>Jan Kardys' Literary Agency</title>

<style type="text/css">
#header {
    float: left;
    width: 1000px;
#Menu_bar {
    float: left;
    width: 190px;
#Page_Content {
    float: right;
    width: 1000px;
    font-family: "MS Serif", "New York", serif;
#footer {
    float: left;
    width: 1000px;
#Main_content {
    float: left;
    width: 395px;
    padding-left: 100px;
#xtra_content {
    float: right;
    width: 395px;
    padding-right: 100px;
    font-family: "MS Serif", "New York", serif;
#container {
    width: 1000px;
    margin: 0 auto;
    background-image: url(file:///C|/Users/james/Documents/DREAMWEAVER SITES/JanKardys.com/Images/Parchment.gif);
    overflow: hidden;
#header_title {
    font-family: "Trebuchet MS", Arial, Helvetica, sans-serif;
    color: #0C3;
    float: left;
#header_menubar {
    float: right;
</style>
<style type="text/css">
body {
</style>
<script src="/js/enhance.js" type="text/javascript"></script>
<script src="http://www.google.com/jsapi" type="text/javascript"></script>
<script src="http://labs.adobe.com/technologies/spry/ui/includes/SpryDOMUtils.js"" type="text/javascript"></script>
<script src="/Spry-UI-1.7/includes/SpryDOMUtils.js" type="text/javascript"></script>
<script src="/Spry-UI-1.7/includes/SpryDOMEffects.js" type="text/javascript"></script>
<script src="http://labs.adobe.com/technologies/spry/ui/includes/SpryWidget.js" type="text/javascript"></script>
<script src="/Spry-UI-1.7/includes/SpryMenu.js" type="text/javascript"></script>
<script src="/Spry-UI-1.7/includes/plugins/MenuBar2/SpryMenuBarKeyNavigationPlugin.js" type="text/javascript"></script>
<script src="/Spry-UI-1.7/includes/plugins/MenuBar2/SpryMenuBarIEWorkaroundsPlugin.js" type="text/javascript"></script>
<script type="text/xml">

</script>
<link href="/css/basic.css" rel="stylesheet" type="text/css" />
<link href="/Spry-UI-1.7/css/Menu/basic/SpryMenuBasic.css" rel="stylesheet" type="text/css" />
<style type="text/css">
/* BeginOAWidget_Instance_2141544: #MenuBar */
/* Settable values for skinning a Basic menu via presets. If presets are not sufficient, most skinning should be done in
    these rules, with the exception of the images used for down or right pointing arrows, which are in the file SpryMenuBasic.css
     These assume the following widget classes for menu layout (set in a preset)
    .MenuBar - Applies to all menubars - default is horizontal bar, all submenus are vertical - 2nd level subs and beyond are pull-right.
    .MenuBarVertical - vertical main bar; all submenus are pull-right.
    You can also pass in extra classnames to set your desired top level menu bar layout. Normally, these are set by using a preset.
    They only apply to horizontal menu bars:
        MenuBarLeftShrink - The menu bar will be horizontally 'shrinkwrapped' to be just large enough to hold its items, and left aligned
        MenuBarRightShrink - Just like MenuBarLeftShrink, but right aligned
        MenuBarFixedLeft - Fixed at a specified width set in the rule '.MenuBarFixedLeft', and left aligned.
        MenuBarFixedCentered - - Fixed at a specified width set in the rule '.MenuBarFixedCentered',
                        and centered in its parent container.
        MenuBarFullwidth - Grows to fill its parent container width.
    In general, all rules specified in this file are prefixed by #MenuBar so they only apply to instances of the widget inserted along
    with the rules. This permits use of multiple MenuBarBasic widgets on the same page with different layouts. Because of IE6 limitations,
    there are a few rules where this was not possible. Those rules are so noted in comments.
#MenuBar {
    background-color:transparent;
    font-family: "Trebuchet MS", Arial, Helvetica, sans-serif; /* Specify fonts on on MenuBar and subMenu MenuItemContainer, so MenuItemContainer,
                                                MenuItem, and MenuItemLabel
                                                at a given level all use same definition for ems.
                                                Note that this means the size is also inherited to child submenus,
                                                so use caution in using relative sizes other than
                                                100% on submenu fonts. */
    font-weight: normal;
    font-size: 16px;
    font-style: normal;
    padding:0;
    border-color: #ffffff #ffffff #ffffff #ffffff;
    border-width:0px;
    border-style: none none none none;
/* Caution: because ID+class selectors do not work properly in IE6, but we want to restrict these rules to just this
widget instance, we have used string-concatenated classnames for our selectors for the layout type of the menubar
in this section. These have very low specificity, so be careful not to accidentally override them. */
.MenuBar br { /* using just a class so it has same specificity as the ".MenuBarFixedCentered br" rule bleow */
    display:none;
.MenuBarLeftShrink {
    float: left; /* shrink to content, as well as float the MenuBar */
    width: auto;
.MenuBarRightShrink {
    float: right; /* shrink to content, as well as float the MenuBar */
    width: auto;
.MenuBarFixedLeft {
    float: left;
    width: 80em;
.MenuBarFixedCentered {
    float: none;
    width: 80em;
    margin-left:auto;
    margin-right:auto;
.MenuBarFixedCentered br {
    clear:both;
    display:block;
.MenuBarFixedCentered .SubMenu br {
    display:none;
.MenuBarFullwidth {
    float: left;
    width: 100%;
/* Top level menubar items - these actually apply to all items, and get overridden for 1st or successive level submenus */
#MenuBar .MenuItemContainer {
    padding: 0px 0px 0px 0px;
    margin: 0;     /* Zero out margin on the item containers. The MenuItem is the active hover area.
                For most items, we have to do top or bottom padding or borders only on the MenuItem
                or a child so we keep the entire submenu tiled with items.
                Setting this to 0 avoids "dead spots" for hovering. */
#MenuBar .MenuItem {
    padding: 0px 0px 0px 0px;
    background-color:transparent;
    border-width:1px;
    border-color: #cccccc #ffffff #cccccc #ffffff;
    border-style: none solid none solid;
#MenuBar .MenuItemFirst {
    border-style: none none none none;
#MenuBar .MenuItemLast {
    border-style: none solid none none;
#MenuBar .MenuItem .MenuItemLabel{
    text-align:center;
    line-height:1.4em;
    color:#33ff66;
    background-color:transparent;
    padding: 6px 15px 6px 15px;
    width: 10em;
    width:auto;
.SpryIsIE6 #MenuBar .MenuItem .MenuItemLabel{
    width:1em; /* Equivalent to min-width in modern browsers */
/* First level submenu items */
#MenuBar .SubMenu .MenuItem {
    font-family: Arial, Helvetica, sans-serif;
    font-weight: normal;
    font-size: 14px;
    font-style: normal;
    background-color:transparent;
    padding:0px 2px 0px 0px;
    border-width:1px;
    border-color: #cccccc #cccccc #cccccc #cccccc;
    /* Border styles are overriden by first and last items */
    border-style: solid solid none solid;
#MenuBar .SubMenu .MenuItemFirst {
    border-style: solid solid none solid;
#MenuBar .SubMenu .MenuItemFirst .MenuItemLabel{
    padding-top: 6px;
#MenuBar .SubMenu .MenuItemLast {
    border-style: solid solid solid solid;
#MenuBar .SubMenu .MenuItemLast .MenuItemLabel{
    padding-bottom: 6px;
#MenuBar .SubMenu .MenuItem .MenuItemLabel{
    text-align:left;
    line-height:1em;
    background-color:transparent;
    color:#00ff33;
    padding: 6px 5px 6px 5px;
    width: 7em;
    width:auto;
/* Hover states for containers, items and labels */
#MenuBar .MenuItemHover {
    background-color: transparent;
    border-color: #cccccc #cccccc #cccccc #cccccc;
#MenuBar .MenuItemWithSubMenu.MenuItemHover .MenuItemLabel{
    background-color: transparent; /* consider exposing this prop separately*/
    color: #000000;
#MenuBar .MenuItemHover .MenuItemLabel{
    background-color: transparent;
    color: #000000;
#MenuBar .SubMenu .MenuItemHover {
    background-color: transparent;
    border-color: #cccccc #cccccc #cccccc #cccccc;
#MenuBar .SubMenu .MenuItemHover .MenuItemLabel{
    background-color: transparent;
    color: #333333;
/* Submenu properties -- First level of submenus */
#MenuBar .SubMenuVisible {
    background-color: transparent;
    min-width:0%; /* This keeps the menu from being skinnier than the parent MenuItemContainer - nice to have but not available on ie6 */
    border-color: #ffffff #ffffff #ffffff #ffffff;
    border-width:0px;
    border-style: none none none none;
#MenuBar.MenuBar .SubMenuVisible {/* For Horizontal menubar only */
    top: 100%;    /* 100% is at the bottom of parent menuItemContainer */
    left:0px; /* 'left' may need tuning depending upon borders or padding applied to menubar MenuItemContainer or MenuItem,
                    and your personal taste.
                    0px will left align the dropdown with the content area of the MenuItemContainer. Assuming you keep the margins 0
                    on MenuItemContainer and MenuItem on the parent
                    menubar, making this equal the sum of the MenuItemContainer & MenuItem padding-left will align
                    the dropdown with the left of the menu item label.*/
    z-index:10;
#MenuBar.MenuBarVertical .SubMenuVisible {
    top: 0px;
    left:100%;
    min-width:0px; /* Do not neeed to match width to parent MenuItemContainer - items will prevent total collapse */
/* Submenu properties -- Second level submenu and beyond - these are visible descendents of .MenuLevel1 */
#MenuBar .MenuLevel1 .SubMenuVisible {
    background-color: transparent;
    min-width:0px; /* Do not neeed to match width to parent MenuItemContainer - items will prevent total collapse*/
    top: 0px;    /* If desired, you can move this down a smidge to separate top item''s submenu from menubar -
                that is really only needed for submenu on first item of MenuLevel1, or you can make it negative to make submenu more
                vertically 'centered' on its invoking item */
    left:100%; /* If you want to shift the submenu left to partially cover its invoking item, you can add a margin-left with a
                negative value to this rule. Alternatively, if you use fixed-width items, you can change this left value
                to use px or ems to get the offset you want. */
/* IE6 rules - you can delete these if you do not want to support IE6 */
/* A note about multiple classes in IE6.
* Some of the rules above use multiple class names on an element for selection, such as "hover" (MenuItemHover) and "has a subMenu" (MenuItemWithSubMenu),
* giving the selector '.MenuItemWithSubMenu.MenuItemHover'.
* Unfortunately IE6 does not support using mutiple classnames in a selector for an element. For a selector such as '.foo.bar.baz', IE6 ignores
* all but the final classname (here, '.baz'), and sets the specificity accordingly, counting just one of those classs as significant. To get around this
* problem, we use the plugin in SpryMenuBarIEWorkaroundsPlugin.js to generate compound classnames for IE6, such as 'MenuItemWithSubMenuHover'.
* Since there are a lot of these needed, the plugin does not generate the extra classes for modern browsers, and we use the CSS2 style mutltiple class
* syntax for that. Since IE6 both applies rules where
* it should not, and gets the specificity wrong too, we have to order rules carefully, so the rule misapplied in IE6 can be overridden.
* So, we put the multiple class rule first. IE6 will mistakenly apply this rule. We follow this with the single-class rule that it would
* mistakenly override, making sure the misinterpreted IE6 specificity is the same as the single-class selector, so the latter wins.
* We then create a copy of the multiple class rule, adding a '.SpryIsIE6' class as context, and making sure the specificity for
* the selector is high enough to beat the single-class rule in the "both classes match" case. We place the IE6 rule at the end of the
* css style block to make it easy to delete if you want to drop IE6 support.
* If you decide you do not need IE6 support, you can get rid of these, as well as the inclusion of the SpryMenuBarIEWorkaroundsPlugin.js script.
* The 'SpryIsIE6' class is placed on the HTML element by the script in SpryMenuBarIEWorkaroundsPlugin.js if the browser is Internet Explorer 6. This avoids the necessity of IE conditional comments for these rules.
.SpryIsIE6 #MenuBar .MenuBarView .MenuItemWithSubMenuHover .MenuItemLabel /* IE6 selector */{
    background-color: transparent; /* consider exposing this prop separately*/
    color: #000000;
.SpryIsIE6 #MenuBar .MenuBarView .SubMenu .MenuItemWithSubMenuHover .MenuItemLabel/* IE6 selector */{
    background-color: transparent; /* consider exposing this prop separately*/
    color: #333333;
.SpryIsIE6 #MenuBar .SubMenu .SubMenu /* IE6 selector */{
    margin-left: -0px; /* Compensates for at least part of an IE6 "double padding" version of the "double margin" bug */
/* EndOAWidget_Instance_2141544 */
</style>


</head>
<body>
<div id= "container">
<div id="header">
<div id="header_title"><h1>Jan kardy's Literary Agency</h1></div>
<div id="header_menubar">
</li>
    </ul>
    
    <ul id="MenuBar">
      <li> <a href="file:///C|/Users/james/Documents/DREAMWEAVER SITES/JanKardys.com/index.html">Home</a></li>
      <li> <a href="file:///C|/Users/james/Documents/DREAMWEAVER SITES/JanKardys.com/about_jankardys.html">About Jan Kardys</a></li>
      <li> <a href="#">Resources</a>
        <ul>
          <li> <a href="/Education_connection.html">Education Connection</a></li>
          <li> <a href="/submission_guidelines.html">Submission Guidelines</a> </li>
          <li> <a href="#">Blogs</a>
            <ul>
              <li> <a href="http://unicornwritersconferencect.blogspot.com/">Unicorn Writers Conference</a></li>
              <li> <a href="http://advancenetworkingunicorn.blogspot.com/">Advanced Netwroking Blog</a></li>
            </ul>
          </li>
          <li> <a href="#">First Steps to Publishing</a></li>
          <li> <a href="#">Library & Publishing Events</a></li>
          <li> <a href="#">Art Gallery</a> </li>
        </ul>
      </li>
      <li> <a href="#">Clients</a></li>
      <li> <a href="#">Contact Jan Kardys</a> </li>
    </ul>
    <script type="text/javascript">
// BeginOAWidget_Instance_2141544: #MenuBar
var MenuBar = new Spry.Widget.MenuBar2("#MenuBar", {
      widgetID: "MenuBar",
      widgetClass: "MenuBar MenuBarLeftShrink",
      insertMenuBarBreak: true,
      mainMenuShowDelay: 200,
      mainMenuHideDelay: 200,
      subMenuShowDelay: 200,
      subMenuHideDelay: 200
// EndOAWidget_Instance_2141544
    </script>
</li>
      </ul>
</div>
</div>
<div id="Page_Content">
<div id="Main_content">hi</div>

<div id="xtra_content">
    <h3>News & Events </h3>
    <p> </p>
</div>
</div>
<div id="footer"> <h6>Webpage designed by James S. Molina</h6></div>
</div>
</body>
</html>
EDUCATION CONNECTION CODE:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />

<title>Jan Kardys' Literary Agency</title>

<style type="text/css">
#header {
    float: left;
    width: 1000px;
#Menu_bar {
    float: left;
    width: 190px;
#Page_Content {
    float: right;
    width: 1000px;
    font-family: "MS Serif", "New York", serif;
#footer {
    float: left;
    width: 1000px;
#Main_content {
    float: left;
    width: 395px;
    padding-left: 100px;
#xtra_content {
    float: right;
    width: 395px;
    padding-right: 100px;
    font-family: "MS Serif", "New York", serif;
#container {
    width: 1000px;
    margin: 0 auto;
    background-image: url(/Images/Parchment.gif);
    overflow: hidden;
#header_title {
    font-family: "Trebuchet MS", Arial, Helvetica, sans-serif;
    color: #0C3;
    float: left;
#header_menubar {
    float: right;
</style>
<style type="text/css">
body {
</style>
<script src="/js/enhance.js" type="text/javascript"></script>
<script src="http://www.google.com/jsapi" type="text/javascript"></script>
<script src="http://labs.adobe.com/technologies/spry/ui/includes/SpryDOMUtils.js"" type="text/javascript"></script>
<script src="/Spry-UI-1.7/includes/SpryDOMUtils.js" type="text/javascript"></script>
<script src="/Spry-UI-1.7/includes/SpryDOMEffects.js" type="text/javascript"></script>
<script src="http://labs.adobe.com/technologies/spry/ui/includes/SpryWidget.js" type="text/javascript"></script>
<script src="/Spry-UI-1.7/includes/SpryMenu.js" type="text/javascript"></script>
<script src="/Spry-UI-1.7/includes/plugins/MenuBar2/SpryMenuBarKeyNavigationPlugin.js" type="text/javascript"></script>
<script src="/Spry-UI-1.7/includes/plugins/MenuBar2/SpryMenuBarIEWorkaroundsPlugin.js" type="text/javascript"></script>
<script type="text/xml">

</script>
<link href="/css/basic.css" rel="stylesheet" type="text/css" />
<link href="/Spry-UI-1.7/css/Menu/basic/SpryMenuBasic.css" rel="stylesheet" type="text/css" />
<style type="text/css">
/* BeginOAWidget_Instance_2141544: #MenuBar */
/* Settable values for skinning a Basic menu via presets. If presets are not sufficient, most skinning should be done in
    these rules, with the exception of the images used for down or right pointing arrows, which are in the file SpryMenuBasic.css
     These assume the following widget classes for menu layout (set in a preset)
    .MenuBar - Applies to all menubars - default is horizontal bar, all submenus are vertical - 2nd level subs and beyond are pull-right.
    .MenuBarVertical - vertical main bar; all submenus are pull-right.
    You can also pass in extra classnames to set your desired top level menu bar layout. Normally, these are set by using a preset.
    They only apply to horizontal menu bars:
        MenuBarLeftShrink - The menu bar will be horizontally 'shrinkwrapped' to be just large enough to hold its items, and left aligned
        MenuBarRightShrink - Just like MenuBarLeftShrink, but right aligned
        MenuBarFixedLeft - Fixed at a specified width set in the rule '.MenuBarFixedLeft', and left aligned.
        MenuBarFixedCentered - - Fixed at a specified width set in the rule '.MenuBarFixedCentered',
                        and centered in its parent container.
        MenuBarFullwidth - Grows to fill its parent container width.
    In general, all rules specified in this file are prefixed by #MenuBar so they only apply to instances of the widget inserted along
    with the rules. This permits use of multiple MenuBarBasic widgets on the same page with different layouts. Because of IE6 limitations,
    there are a few rules where this was not possible. Those rules are so noted in comments.
#MenuBar {
    background-color:transparent;
    font-family: "Trebuchet MS", Arial, Helvetica, sans-serif; /* Specify fonts on on MenuBar and subMenu MenuItemContainer, so MenuItemContainer,
                                                MenuItem, and MenuItemLabel
                                                at a given level all use same definition for ems.
                                                Note that this means the size is also inherited to child submenus,
                                                so use caution in using relative sizes other than
                                                100% on submenu fonts. */
    font-weight: normal;
    font-size: 16px;
    font-style: normal;
    padding:0;
    border-color: #ffffff #ffffff #ffffff #ffffff;
    border-width:0px;
    border-style: none none none none;
/* Caution: because ID+class selectors do not work properly in IE6, but we want to restrict these rules to just this
widget instance, we have used string-concatenated classnames for our selectors for the layout type of the menubar
in this section. These have very low specificity, so be careful not to accidentally override them. */
.MenuBar br { /* using just a class so it has same specificity as the ".MenuBarFixedCentered br" rule bleow */
    display:none;
.MenuBarLeftShrink {
    float: left; /* shrink to content, as well as float the MenuBar */
    width: auto;
.MenuBarRightShrink {
    float: right; /* shrink to content, as well as float the MenuBar */
    width: auto;
.MenuBarFixedLeft {
    float: left;
    width: 80em;
.MenuBarFixedCentered {
    float: none;
    width: 80em;
    margin-left:auto;
    margin-right:auto;
.MenuBarFixedCentered br {
    clear:both;
    display:block;
.MenuBarFixedCentered .SubMenu br {
    display:none;
.MenuBarFullwidth {
    float: left;
    width: 100%;
/* Top level menubar items - these actually apply to all items, and get overridden for 1st or successive level submenus */
#MenuBar .MenuItemContainer {
    padding: 0px 0px 0px 0px;
    margin: 0;     /* Zero out margin on the item containers. The MenuItem is the active hover area.
                For most items, we have to do top or bottom padding or borders only on the MenuItem
                or a child so we keep the entire submenu tiled with items.
                Setting this to 0 avoids "dead spots" for hovering. */
#MenuBar .MenuItem {
    padding: 0px 0px 0px 0px;
    background-color:transparent;
    border-width:1px;
    border-color: #cccccc #ffffff #cccccc #ffffff;
    border-style: none solid none solid;
#MenuBar .MenuItemFirst {
    border-style: none none none none;
#MenuBar .MenuItemLast {
    border-style: none solid none none;
#MenuBar .MenuItem .MenuItemLabel{
    text-align:center;
    line-height:1.4em;
    color:#33ff66;
    background-color:transparent;
    padding: 6px 15px 6px 15px;
    width: 10em;
    width:auto;
.SpryIsIE6 #MenuBar .MenuItem .MenuItemLabel{
    width:1em; /* Equivalent to min-width in modern browsers */
/* First level submenu items */
#MenuBar .SubMenu .MenuItem {
    font-family: Arial, Helvetica, sans-serif;
    font-weight: normal;
    font-size: 14px;
    font-style: normal;
    background-color:transparent;
    padding:0px 2px 0px 0px;
    border-width:1px;
    border-color: #cccccc #cccccc #cccccc #cccccc;
    /* Border styles are overriden by first and last items */
    border-style: solid solid none solid;
#MenuBar .SubMenu .MenuItemFirst {
    border-style: solid solid none solid;
#MenuBar .SubMenu .MenuItemFirst .MenuItemLabel{
    padding-top: 6px;
#MenuBar .SubMenu .MenuItemLast {
    border-style: solid solid solid solid;
#MenuBar .SubMenu .MenuItemLast .MenuItemLabel{
    padding-bottom: 6px;
#MenuBar .SubMenu .MenuItem .MenuItemLabel{
    text-align:left;
    line-height:1em;
    background-color:transparent;
    color:#00ff33;
    padding: 6px 5px 6px 5px;
    width: 7em;
    width:auto;
/* Hover states for containers, items and labels */
#MenuBar .MenuItemHover {
    background-color: transparent;
    border-color: #cccccc #cccccc #cccccc #cccccc;
#MenuBar .MenuItemWithSubMenu.MenuItemHover .MenuItemLabel{
    background-color: transparent; /* consider exposing this prop separately*/
    color: #000000;
#MenuBar .MenuItemHover .MenuItemLabel{
    background-color: transparent;
    color: #000000;
#MenuBar .SubMenu .MenuItemHover {
    background-color: transparent;
    border-color: #cccccc #cccccc #cccccc #cccccc;
#MenuBar .SubMenu .MenuItemHover .MenuItemLabel{
    background-color: transparent;
    color: #333333;
/* Submenu properties -- First level of submenus */
#MenuBar .SubMenuVisible {
    background-color: transparent;
    min-width:0%; /* This keeps the menu from being skinnier than the parent MenuItemContainer - nice to have but not available on ie6 */
    border-color: #ffffff #ffffff #ffffff #ffffff;
    border-width:0px;
    border-style: none none none none;
#MenuBar.MenuBar .SubMenuVisible {/* For Horizontal menubar only */
    top: 100%;    /* 100% is at the bottom of parent menuItemContainer */
    left:0px; /* 'left' may need tuning depending upon borders or padding applied to menubar MenuItemContainer or MenuItem,
                    and your personal taste.
                    0px will left align the dropdown with the content area of the MenuItemContainer. Assuming you keep the margins 0
                    on MenuItemContainer and MenuItem on the parent
                    menubar, making this equal the sum of the MenuItemContainer & MenuItem padding-left will align
                    the dropdown with the left of the menu item label.*/
    z-index:10;
#MenuBar.MenuBarVertical .SubMenuVisible {
    top: 0px;
    left:100%;
    min-width:0px; /* Do not neeed to match width to parent MenuItemContainer - items will prevent total collapse */
/* Submenu properties -- Second level submenu and beyond - these are visible descendents of .MenuLevel1 */
#MenuBar .MenuLevel1 .SubMenuVisible {
    background-color: transparent;
    min-width:0px; /* Do not neeed to match width to parent MenuItemContainer - items will prevent total collapse*/
    top: 0px;    /* If desired, you can move this down a smidge to separate top item''s submenu from menubar -
                that is really only needed for submenu on first item of MenuLevel1, or you can make it negative to make submenu more
                vertically 'centered' on its invoking item */
    left:100%; /* If you want to shift the submenu left to partially cover its invoking item, you can add a margin-left with a
                negative value to this rule. Alternatively, if you use fixed-width items, you can change this left value
                to use px or ems to get the offset you want. */
/* IE6 rules - you can delete these if you do not want to support IE6 */
/* A note about multiple classes in IE6.
* Some of the rules above use multiple class names on an element for selection, such as "hover" (MenuItemHover) and "has a subMenu" (MenuItemWithSubMenu),
* giving the selector '.MenuItemWithSubMenu.MenuItemHover'.
* Unfortunately IE6 does not support using mutiple classnames in a selector for an element. For a selector such as '.foo.bar.baz', IE6 ignores
* all but the final classname (here, '.baz'), and sets the specificity accordingly, counting just one of those classs as significant. To get around this
* problem, we use the plugin in SpryMenuBarIEWorkaroundsPlugin.js to generate compound classnames for IE6, such as 'MenuItemWithSubMenuHover'.
* Since there are a lot of these needed, the plugin does not generate the extra classes for modern browsers, and we use the CSS2 style mutltiple class
* syntax for that. Since IE6 both applies rules where
* it should not, and gets the specificity wrong too, we have to order rules carefully, so the rule misapplied in IE6 can be overridden.
* So, we put the multiple class rule first. IE6 will mistakenly apply this rule. We follow this with the single-class rule that it would
* mistakenly override, making sure the misinterpreted IE6 specificity is the same as the single-class selector, so the latter wins.
* We then create a copy of the multiple class rule, adding a '.SpryIsIE6' class as context, and making sure the specificity for
* the selector is high enough to beat the single-class rule in the "both classes match" case. We place the IE6 rule at the end of the
* css style block to make it easy to delete if you want to drop IE6 support.
* If you decide you do not need IE6 support, you can get rid of these, as well as the inclusion of the SpryMenuBarIEWorkaroundsPlugin.js script.
* The 'SpryIsIE6' class is placed on the HTML element by the script in SpryMenuBarIEWorkaroundsPlugin.js if the browser is Internet Explorer 6. This avoids the necessity of IE conditional comments for these rules.
.SpryIsIE6 #MenuBar .MenuBarView .MenuItemWithSubMenuHover .MenuItemLabel /* IE6 selector */{
    background-color: transparent; /* consider exposing this prop separately*/
    color: #000000;
.SpryIsIE6 #MenuBar .MenuBarView .SubMenu .MenuItemWithSubMenuHover .MenuItemLabel/* IE6 selector */{
    background-color: transparent; /* consider exposing this prop separately*/
    color: #333333;
.SpryIsIE6 #MenuBar .SubMenu .SubMenu /* IE6 selector */{
    margin-left: -0px; /* Compensates for at least part of an IE6 "double padding" version of the "double margin" bug */
/* EndOAWidget_Instance_2141544 */
</style>


</head>
<body>
<div id= "container">
<div id="header">
<div id="header_title"><h1>Jan kardy's Literary Agency</h1></div>
<div id="header_menubar">
</li>
    </ul>
    
    <ul id="MenuBar">
      <li> <a href="/index.html">Home</a></li>
      <li> <a href="/about_jankardys.html">About Jan Kardys</a></li>
      <li> <a href="#">Resources</a>
        <ul>
          <li> <a href="/Education_connection.html">Education Connection</a></li>
          <li> <a href="/submission_guidelines.html">Submission Guidelines</a> </li>
          <li> <a href="#">Blogs</a>
            <ul>
              <li> <a href="http://unicornwritersconferencect.blogspot.com/">Unicorn Writers Conference</a></li>
              <li> <a href="http://advancenetworkingunicorn.blogspot.com/">Advanced Netwroking Blog</a></li>
            </ul>
          </li>
          <li> <a href="#">First Steps to Publishing</a></li>
          <li> <a href="#">Library & Publishing Events</a></li>
          <li> <a href="#">Art Gallery</a> </li>
        </ul>
      </li>
      <li> <a href="#">Clients</a></li>
      <li> <a href="#">Contact Jan Kardys</a> </li>
    </ul>
    <script type="text/javascript">
// BeginOAWidget_Instance_2141544: #MenuBar
var MenuBar = new Spry.Widget.MenuBar2("#MenuBar", {
      widgetID: "MenuBar",
      widgetClass: "MenuBar MenuBarLeftShrink",
      insertMenuBarBreak: true,
      mainMenuShowDelay: 200,
      mainMenuHideDelay: 200,
      subMenuShowDelay: 200,
      subMenuHideDelay: 200
// EndOAWidget_Instance_2141544
    </script>
</li>
      </ul>
</div>
</div>
<div id="Page_Content">
<div id="Main_content"><img src="/Images/jankardys.jpg" width="171" height="234" alt="Jan_kardys_pictuer" /></div>

<div id="xtra_content">
    <center><h3>Signed Book Deal</h3>
    <p><a href="http://jankardys.com/Advance_Royalties.html" title="Advance_Royalties.html">Advance/Royalties</a></p>
    <p><a href="http://jankardys.com/Author_Quotes.html" title="Author_Quotes.html">Author Quotes</a></p>
    <p><a href="http://jankardys.com/Book_Deal.html" title="Book_Deal.html">Book Deal</a></p>
    <p><a href="http://jankardys.com/Copyright_Information.html" title="Copyright_Information.html">Copyright Information</a></p>
    <p><a href="http://jankardys.com/Editorial_Assistance.html" title="Editorial_Assistance.html">Freelance Editorial Assistance</a></p>
    <p><a href="http://jankardys.com/Electronic_Rights.html" title="Electronic_Rights.html">Electronic Rights Guidelines</a></p>
    <p><a href="http://jankardys.com/Google_Products.html" title="Google_Products.html">Google Products</a></p>
    <p><a href="http://jankardys.com/Out_of_Print_Reversions.html" title="Out_of_Print_Reversions.html">Out of Print Reversions</a></p>
    <p><a href="http://jankardys.com/Permissions.html" title="Permissions.html">Permissions</a></p>
    <p><a href="http://jankardys.com/Photo_release.html" title="Photo_release.html">Photo Release</a></p>
    <p><a href="http://jankardys.com/Return_of_Advance.html" title="Return_of_Advance.html">Return of Advance</a></p>
    <p><a href="http://jankardys.com/Subrights_Checklist.html" title="Subrights_Checklist.html">Subrights Checklist</a></p></center>
    <p> </p>
    <p> </p>
</div>
</div>
<div id="footer"> <h6>Webpage designed by James S. Molina</h6></div>
</div>
</body>
</html>

Added a spry menu bar and site works in firefox but not in chrome or IE. Please help

Hello,
I'm a photographer by trade and have only picked up enough web design knowledge in order to build a website that isn't distracting to my photographs and is simple to update and mantain. Please breakdown any answers to my questions in very simple terms.
To start off here is a link to my site for reference. www.cechternach.com
1. My Biggest problem right now is that my site works in firefox but appears as a blank white page in chrome and in IE it only shows my background color.
I'm assuming that this has something to do with the spry menu bar I added. The galleries, banner, and footer were all part of a previous version of this website that didn't use the menu bar. I actually used png's exported from an illustrator as buttons. I've been wrestling with this menu bar for a few days now. I had an issue with the menubar forcing down the gallery below it. that was fixed by changing a position value from relative to absolute in the menubar css. Then I couldn't see the submenu over the galleries. I think I fixed that with a wmode change but I"m not sure if I did that right. I believe i needed to change that in the object and embed part of the code. One spot for certain browsers and the other spot for other browsers. I was a little confused on this because i also read that i needed to change the wmode in the javascript file in dreamweaver cs4 which is what i'm using. Whatever wmode I changed it seemed to work in firefox. The submenu background was showing up transparent but i fixed that in the menubar css.
2. I would like the submenu's to have a semi transparent blurred background effect. Is this possible with a spry menu bar?
3. How do I center my text in the submenu?
4. My menu bar buttons should be the same font as my name in my banner. It looks fine on my computer that has that font loaded but on other computers I was testing the site on the menubar buttons show up as a default font. How can i fix this?
5. Is there any way to get rid of the grey lines that show up around my slideshow pro galleries and menu bar buttons when they are clicked?
The last four questions aren't as important as the first one. I may be upsetting the flow of the forum as well. Please let me know if I'm not following procedure with any of my questions. Feel free to point out any other problems you see with my page. I'm trying to learn this as I go. Thanks in advance.

Spry widgets, which includes the SpryMenuBar, in their original state do not pose any problem in any browser!
Widgets contain two parts
JavaScript which drives the widget
CSS which styles the widget to individual tastes
The most common reason for a widget to misbehave especially in IE is because the inexperienced web developer has upset the delicate balance of the CSS. I say delicate, because in the original, great care has been taken by the Spry team to ensure cross browser compatibility.
There are other reasons why a whole page can misbehave. In these cases, the culprit should be sought outside of the Spry framework.
When trouble shooting, I would first of all comment out all of the Spry Spry parts and test the page in IE. If it does work after that, then yes come back here and we will have a look at the SpryMenuBarHorizontal.css for you.
If it doesn't work after disabling Spry, then have a look at the coding and the CSS for your page and fix that.
I hope this helps.
Ben

Oops - spry menu bar 2.0 does not display correctly when loaded

Oops - obviously I'm new at this. I think I got my graphics loaded now.
Dear Sirs:
I notice bzz31 had a pretty complicated post, so perhaps someone can help me with my complicated problem that has been vexing me for months. I tried the Spry Menu Bar 1.0, but it was impossible for me to edit, and I was delighted to see Spry Menu Bar 2.0 come out. However the 2.0 version has been frustrating me as well.
I can get my menu bar to display properly in Live View, as shown below.
However when I load everything onto the server, the menu bar does not display correctly, as shown below:
I don't quite understand the code "file:///" but I interpret it to mean that the Spry-UI-1.7 folder is in the topmost folder of MacPro5-Docs, which is my hard drive. Here's the code I'm having trouble with:
Here's my computer directory, shown below:
Since my index file is two folders down from Spry-UI-1.7, I loaded the files onto the server similarly, as shown in the next three pictures:
(The picture below is the same as the one just above, but now you can see the path from index to Spry-UI-1.7.)
I would be most appreciative if someone can help me.
Thank you.

Have a look at the following links
<script src="file:///MacProG5-Docs/Spry-UI-1.7/includes/SpryDOMUtils.js" type="text/javascript"></script>
<script src="file:///MacProG5-Docs/Spry-UI-1.7/includes/SpryDOMEffects.js" type="text/javascript"></script>
<script src="file:///MacProG5-Docs/Spry-UI-1.7/includes/SpryWidget.js" type="text/javascript"></script>
<script src="file:///MacProG5-Docs/Spry-UI-1.7/includes/SpryMenu.js" type="text/javascript"></script>
<script src="file:///MacProG5-Docs/Spry-UI-1.7/includes/plugins/MenuBar2/SpryMenuBarKeyNavigationPlugin.js" type="text/javascript"></script>
<script src="file:///MacProG5-Docs/Spry-UI-1.7/includes/plugins/MenuBar2/SpryMenuBarIEWorkaroundsPlugin.js" type="text/javascript"></script>
<link href="file:///MacProG5-Docs/Spry-UI-1.7/css/Menu/basic/SpryMenuBasic.css" rel="stylesheet" type="text/css" />
Each of the above points to a file on your local system and cannot be found by the remote server.
Replace the red coloured parts with http://www.twhsbands.org/ will remedy the situation.
You also have some remnants of the other SpryMenuBar that should be removed from your markup.
Gramps
Wel, so much for the red coloured parts, they did not show up.
The red coloured parts read file:///MacProG5-Docs/

DW9 quits when adding Spry Menu elements

Similar Messages

Maybe you are looking for