Problem with Arguments and relationships

I don't get expected output when using an argument that is "filtering" based on a field that is available through a relationship.

To replicate the problem:

Create 2 content types A and B:

Content Type: A
Date Field
Node Reference: (To Content Type B)

Content Type: B
Date Field

Create a view X with:
Relationships: Between A and B (call it A->B)
Fields: Node Title, B.date (accessed through A->B relationship)
Filters: Node type == A, Exposed Date Filter for A.date (defaulted to the value you set for A.date when you create the sample A node)
Argument: B.date == Defaulted Argument Value (the value you set for B.date when you create the sample B node)

Create a sample node A and B, and link them up.

Your view should return the sample A node, and the

Your view SHOULD return the title of the A node, and display the corresponding B node's date, but it doesn't.
Now flip the argument and exposed filter fields. So that the argument is checking against the A node's date (which doesn't require a relationship), and the exposed filter is checking against the B node's date (which will require using the relationship that is already set up). This should result in your view returning the expected output. It's only when the argument uses the relationship do you have a problem.

I have the latest -dev version (from april 21st). I have made one patch, referenced in #385688: Views filters & arguments not working when using a date relationship. to fix a problem with exposed date filters and relationships. Perhaps this a similiar type of problem? Let me know if you need any other information.