> Could this be inserted into a next patch or is this workaround final.... I'm still not sure why the workaround is necessary, but when I know how to get this to work without it, it'll go into a patch. --ryan.